All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Arnd Bergmann <arnd@arndb.de>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] sh: Fix missing prototypes (part three)
Date: Mon, 13 May 2024 15:20:52 +0200	[thread overview]
Message-ID: <cover.1715606232.git.geert+renesas@glider.be> (raw)

	Hi all,

This patch series fixes more "no previous prototype for <foo>" warnings
when building a kernel for SuperH, namely when building j2_defconfig.

Thanks for your comments!

Geert Uytterhoeven (3):
  sh: of-generic: Add missing #include <asm/clock.h>
  sh: smp: Protect setup_profiling_timer() by CONFIG_PROFILING
  sh: setup: Add missing forward declaration for sh_fdt_init()

 arch/sh/boards/of-generic.c | 2 ++
 arch/sh/include/asm/setup.h | 1 +
 arch/sh/kernel/smp.c        | 2 ++
 3 files changed, 5 insertions(+)

-- 
2.34.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2024-05-13 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 13:20 Geert Uytterhoeven [this message]
2024-05-13 13:20 ` [PATCH 1/3] sh: of-generic: Add missing #include <asm/clock.h> Geert Uytterhoeven
2024-05-13 13:20 ` [PATCH 2/3] sh: smp: Protect setup_profiling_timer() by CONFIG_PROFILING Geert Uytterhoeven
2024-05-13 13:20 ` [PATCH 3/3] sh: setup: Add missing forward declaration for sh_fdt_init() Geert Uytterhoeven
2024-05-13 13:30 ` [PATCH 0/3] sh: Fix missing prototypes (part three) John Paul Adrian Glaubitz

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=cover.1715606232.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=arnd@arndb.de \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.