From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Rich Felker <dalias@libc.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
Rob Landley <rob@landley.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: SH patches for 5.12
Date: Tue, 2 Mar 2021 15:32:20 +0100 [thread overview]
Message-ID: <66978ea5-dce2-0501-677d-7d10d8674bf9@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdXEbD13AG9m1PJVyVpg3=QUDMHG_LQuEyYc2bwrLHU-xQ@mail.gmail.com>
On 3/2/21 3:17 PM, Geert Uytterhoeven wrote:
>> Maybe it's just a duplicate of a warning that was already there and
>> that should be dealt with too.
>
> I think that can be ignored safely: similar functions like __ashrdi3()
> also lack forward declarations on SH.
>
> Looks like only microblaze and powerpc do have forward declarations
> for the gcc helpers:
> arch/microblaze/lib/libgcc.h
> arch/powerpc/include/asm/asm-prototypes.h
>
> One day we may move them to asm-generic, and start using them
> everywhere...
OK. Then let's send the PR for 5.12 and tackle this for 5.13?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2021-03-03 3:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 9:42 SH patches for 5.12 John Paul Adrian Glaubitz
2021-02-21 19:44 ` Rob Landley
2021-02-23 0:56 ` Rich Felker
2021-03-02 8:51 ` John Paul Adrian Glaubitz
2021-03-02 14:03 ` Rich Felker
2021-03-02 14:17 ` Geert Uytterhoeven
2021-03-02 14:27 ` Arnd Bergmann
2021-03-02 14:33 ` Geert Uytterhoeven
2021-03-02 14:38 ` Arnd Bergmann
2021-03-02 14:48 ` Rich Felker
2021-03-02 15:03 ` Geert Uytterhoeven
2021-03-02 14:52 ` Geert Uytterhoeven
2021-03-02 14:32 ` John Paul Adrian Glaubitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66978ea5-dce2-0501-677d-7d10d8674bf9@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).