mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	linux-kernel@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Arnd Bergmann <arnd@arndb.de>, Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/7 v4] sh: remove sh5/sh64 last fragments
Date: Thu, 16 Mar 2023 09:44:37 -0700	[thread overview]
Message-ID: <ef8fbda8-cace-1db3-9161-abd2e75dcf13@infradead.org> (raw)
In-Reply-To: <c16434108aaf639782f905ae45e94ea9d58621f1.camel@physik.fu-berlin.de>

Hi--

On 3/16/23 06:23, John Paul Adrian Glaubitz wrote:
> Hi Randy!
> 
> On Sun, 2023-03-05 at 20:00 -0800, Randy Dunlap wrote:
>> A previous patch removed most of the sh5 (sh64) support from the
>> kernel tree. Now remove the last stragglers.
>>
>> Fixes: 37744feebc08 ("sh: remove sh5 support")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Rich Felker <dalias@libc.org>
>> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
>> Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
>> Cc: linux-sh@vger.kernel.org
>> Acked-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
>> ---
>> v2: update after adding the parisc64 alias to kbuild.rst
>> v3: skipped
>> v4: refresh & resend
>>
>>  Documentation/kbuild/kbuild.rst                           |    1 -
>>  Documentation/scheduler/sched-arch.rst                    |    2 --
>>  Documentation/translations/zh_CN/scheduler/sched-arch.rst |    2 --
>>  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 +-
>>  8 files changed, 2 insertions(+), 21 deletions(-)
>>
>> diff -- a/Documentation/kbuild/kbuild.rst b/Documentation/kbuild/kbuild.rst
>> --- a/Documentation/kbuild/kbuild.rst
>> +++ b/Documentation/kbuild/kbuild.rst
>> @@ -161,7 +161,6 @@ But some architectures such as x86 and s
>>  
>>  - x86: i386 for 32 bit, x86_64 for 64 bit
>>  - parisc: parisc64 for 64 bit
>> -- sh: sh for 32 bit, sh64 for 64 bit
>>  - sparc: sparc32 for 32 bit, sparc64 for 64 bit
>>  
>>  CROSS_COMPILE
> 
> This hunk doesn't apply anymore since the parisc part has been dropped although I can't
> find the commit for that. Could you rebase your patch, please?

The parisc part has not been dropped. It's in linux-next but not yet in mainline.
(commit 49deed336ef9a)

Do you want this patch to apply to mainline? (I created it in linux-next.)
I can do that in a few hours. I'm busy ATM.

I suppose there will be a merge conflict between parisc and SH.


> Apologies that I didn't have the time earlier to start looking at this series!

No problem. We'll get there.  Thanks.

-- 
~Randy

  reply	other threads:[~2023-03-16 16:45 UTC|newest]

Thread overview: 34+ 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 1/7 v4] sh: SH2007: drop the bad URL info Randy Dunlap
2023-03-19 19:22   ` John Paul Adrian Glaubitz
2023-03-06  4:00 ` [PATCH 2/7 v4] sh: nmi_debug: fix return value of __setup handler Randy Dunlap
2023-03-19 19:32   ` John Paul Adrian Glaubitz
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-06  4:00 ` [PATCH 4/7 v4] sh: math-emu: fix macro redefined warning Randy Dunlap
2023-03-19 19:49   ` John Paul Adrian Glaubitz
2023-03-06  4:00 ` [PATCH 5/7 v4] sh: remove sh5/sh64 last fragments Randy Dunlap
2023-03-16 13:23   ` John Paul Adrian Glaubitz
2023-03-16 16:44     ` Randy Dunlap [this message]
2023-03-16 16:52       ` John Paul Adrian Glaubitz
2023-03-16 20:43         ` Randy Dunlap
2023-03-16 20:46           ` John Paul Adrian Glaubitz
2023-03-17  7:31             ` Geert Uytterhoeven
2023-03-17  7:51               ` John Paul Adrian Glaubitz
2023-03-19 19:50   ` John Paul Adrian Glaubitz
2023-03-06  4:00 ` [PATCH 6/7 v4] sh: fix Kconfig entry for NUMA => SMP Randy Dunlap
2023-03-19 20:20   ` John Paul Adrian Glaubitz
2023-03-20 20:13     ` John Paul Adrian Glaubitz
2023-03-20 20:17       ` Randy Dunlap
2023-03-06  4:00 ` [PATCH 7/7 v4] sh: mcount.S: fix build error when PRINTK is not enabled Randy Dunlap
2023-03-19 20:49   ` John Paul Adrian Glaubitz
2023-03-20  8:16     ` Geert Uytterhoeven
2023-03-20  9:13       ` John Paul Adrian Glaubitz
2023-03-20 12:42         ` Geert Uytterhoeven
2023-03-20 12:43           ` Geert Uytterhoeven
2023-03-20 13:32           ` John Paul Adrian Glaubitz
2023-03-20 20:10           ` John Paul Adrian Glaubitz
2023-03-20 20:09   ` 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

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=ef8fbda8-cace-1db3-9161-abd2e75dcf13@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=arnd@arndb.de \
    --cc=dalias@libc.org \
    --cc=geert+renesas@glider.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®