From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
linux-sh@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/7 v4] sh: various doc, build, init fixes
Date: Thu, 23 Mar 2023 10:41:03 +0100 [thread overview]
Message-ID: <075155911e5be40a7f74cc0d05003f8683d784e0.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20230306040037.20350-1-rdunlap@infradead.org>
Hi Randy!
On Sun, 2023-03-05 at 20:00 -0800, Randy Dunlap wrote:
> All of these patches have been sent previously, anywhere from
> one to 3 times. All patches are now called "v4".
>
> This refresh/resend is to assist the new SH maintainer.
>
> [PATCH 1/7 v4] sh: SH2007: drop the bad URL info
> [PATCH 2/7 v4] sh: nmi_debug: fix return value of __setup handler
> [PATCH 3/7 v4] sh: init: use OF_EARLY_FLATTREE for early init
> [PATCH 4/7 v4] sh: math-emu: fix macro redefined warning
> [PATCH 5/7 v4] sh: remove sh5/sh64 last fragments
> [PATCH 6/7 v4] sh: fix Kconfig entry for NUMA => SMP
> [PATCH 7/7 v4] sh: mcount.S: fix build error when PRINTK is not enabled
>
> diffstat:
> Documentation/kbuild/kbuild.rst | 1 -
> Documentation/scheduler/sched-arch.rst | 2 --
> Documentation/translations/zh_CN/scheduler/sched-arch.rst | 2 --
> arch/sh/Kconfig | 4 ++++
> arch/sh/Kconfig.debug | 2 +-
> arch/sh/boards/Kconfig | 1 -
> arch/sh/kernel/head_32.S | 6 +++---
> arch/sh/kernel/nmi_debug.c | 4 ++--
> arch/sh/kernel/setup.c | 4 ++--
> arch/sh/math-emu/sfp-util.h | 4 ----
> scripts/checkstack.pl | 7 -------
> tools/perf/arch/common.c | 2 --
> tools/scripts/Makefile.arch | 5 -----
> tools/testing/selftests/mm/Makefile | 2 +-
> tools/testing/selftests/mm/run_vmtests.sh | 2 +-
> 15 files changed, 14 insertions(+), 34 deletions(-)
>
> Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> Cc: Rich Felker <dalias@libc.org>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
> Cc: linux-sh@vger.kernel.org
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: devicetree@vger.kernel.org
> Cc: Arnd Bergmann <arnd@arndb.de>
All applied to sh-linux/for-next now except for patch number 6.
Apologies that it took so long, I'm still learning :-).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2023-03-23 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 4:00 [PATCH 0/7 v4] sh: various doc, build, init fixes Randy Dunlap
2023-03-06 4:00 ` [PATCH 3/7 v4] sh: init: use OF_EARLY_FLATTREE for early init Randy Dunlap
2023-03-19 19:48 ` John Paul Adrian Glaubitz
2023-03-07 15:18 ` [PATCH 0/7 v4] sh: various doc, build, init fixes John Paul Adrian Glaubitz
2023-03-16 13:26 ` John Paul Adrian Glaubitz
2023-03-23 9:41 ` 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=075155911e5be40a7f74cc0d05003f8683d784e0.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=rdunlap@infradead.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 NNTP newsgroup(s).