From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] sh: Fix missing prototypes (part two)
Date: Thu, 02 May 2024 12:26:50 +0200 [thread overview]
Message-ID: <84b635b9706205147038bbc152aee4a2da92c2ac.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <cover.1709579038.git.geert+renesas@glider.be>
On Mon, 2024-03-04 at 20:10 +0100, Geert Uytterhoeven wrote:
> Hi all,
>
> This patch series fixes more "no previous prototype for <foo>" warnings
> when building a kernel for SuperH, and is a follow-up to [1].
>
> This has been boot-tested on landisk and on qemu/rts7751r2d.
>
> Thanks for your comments!
>
> [1] "[PATCH 00/20] sh: Fix missing prototypes"
> https://lore.kernel.org/r/cover.1709326528.git.geert+renesas@glider.be>
>
> Geert Uytterhoeven (7):
> sh: cache: Move forward declarations to <asm/cacheflush.h>
> sh: traps: Make is_dsp_inst() static
> sh: mach-highlander: Add missing #include <mach/highlander.h>
> sh: mach-sh03: Make sh03_rtc_settimeofday() static
> sh: sh7757lcr: Make init_sh7757lcr_IRQ() static
> sh: sh7757: Add missing #include <asm/mmzone.h>
> sh: sh7785lcr: Make init_sh7785lcr_IRQ() static
>
> arch/sh/boards/board-sh7757lcr.c | 2 +-
> arch/sh/boards/board-sh7785lcr.c | 2 +-
> arch/sh/boards/mach-highlander/pinmux-r7785rp.c | 1 +
> arch/sh/boards/mach-sh03/rtc.c | 2 +-
> arch/sh/include/asm/cacheflush.h | 12 ++++++++++++
> arch/sh/kernel/cpu/sh4a/setup-sh7723.c | 3 +++
> arch/sh/kernel/cpu/sh4a/setup-sh7724.c | 1 +
> arch/sh/kernel/cpu/sh4a/setup-sh7757.c | 3 +++
> arch/sh/kernel/traps_32.c | 4 ++--
> arch/sh/mm/cache-sh4.c | 2 --
> arch/sh/mm/cache-shx3.c | 1 +
> arch/sh/mm/cache.c | 14 --------------
> 12 files changed, 26 insertions(+), 21 deletions(-)
Applied to my sh-linux tree in the for-next branch.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2024-05-02 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 19:10 [PATCH 0/7] sh: Fix missing prototypes (part two) Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 1/7] sh: cache: Move forward declarations to <asm/cacheflush.h> Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 2/7] sh: traps: Make is_dsp_inst() static Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 3/7] sh: mach-highlander: Add missing #include <mach/highlander.h> Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 4/7] sh: mach-sh03: Make sh03_rtc_settimeofday() static Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 5/7] sh: sh7757lcr: Make init_sh7757lcr_IRQ() static Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 6/7] sh: sh7757: Add missing #include <asm/mmzone.h> Geert Uytterhoeven
2024-03-04 19:10 ` [PATCH 7/7] sh: sh7785lcr: Make init_sh7785lcr_IRQ() static Geert Uytterhoeven
2024-05-01 16:49 ` [PATCH 0/7] sh: Fix missing prototypes (part two) John Paul Adrian Glaubitz
2024-05-02 10:26 ` 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=84b635b9706205147038bbc152aee4a2da92c2ac.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).