From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Rich Felker <dalias@libc.org>,
Christoph Hellwig <hch@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux-sh list <linux-sh@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, Rob Landley <rob@landley.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Fri, 5 Jun 2020 17:50:30 -0700 [thread overview]
Message-ID: <20200605175030.feba7dc6fc1233b815c72afb@linux-foundation.org> (raw)
In-Reply-To: <CAMuHMdVTWz33sbn2PPvcNW8KnAcNFvv31yj-z5V3VJ87Xv=tjQ@mail.gmail.com>
On Fri, 5 Jun 2020 20:23:07 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Adrian,
>
> On Fri, Jun 5, 2020 at 7:58 PM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> > On 6/5/20 5:59 PM, Rich Felker wrote:
> > >> Ah, sorry, I missed that. You're right, it should probably go through
> > >> someone else's tree then.
> > >
> > > Do you know if it's needed to un-break sh4? If so we should push to
> > > get whoever has jurisdiction over it to include it; otherwise I'm
> > > indifferent.
>
> I think the above is about the asm-generic/vmlinux.lds.h patch?
> https://marc.info/?l=linux-sh&m=158429470221261&w=2
>
> That one falls under Arnd's jurisdiction.
> And AFAIUC, it matters for recent binutils only? So Arnd should know.
>
Aligning RO_AFTER_INIT_DATA is simply a no-brainer:
--- a/include/asm-generic/vmlinux.lds.h~include-asm-generic-vmlinuxldsh-align-ro_after_init
+++ a/include/asm-generic/vmlinux.lds.h
@@ -374,6 +374,7 @@
*/
#ifndef RO_AFTER_INIT_DATA
#define RO_AFTER_INIT_DATA \
+ . = ALIGN(8); \
__start_ro_after_init = .; \
*(.data..ro_after_init) \
JUMP_TABLE_DATA \
So I'll send this in to Linus for 5.8-rc1. And I think I'll add a cc:stable to
it, so people can use older kernels with newer toolchains.
I still have a few other sh patches sitting here:
https://ozlabs.org/~akpm/mmotm/broken-out/sh-clkfwk-remove-r8-r16-r32.patch
https://ozlabs.org/~akpm/mmotm/broken-out/sh-remove-call-to-memset-after-dma_alloc_coherent.patch
https://ozlabs.org/~akpm/mmotm/broken-out/sh-use-generic-strncpy.patch
https://ozlabs.org/~akpm/mmotm/broken-out/sh-add-missing-export_symbol-for-__delay.patch
What should I do with those?
prev parent reply other threads:[~2020-06-06 0:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 22:19 [GIT PULL] sh: remove sh5 support Arnd Bergmann
2020-04-24 22:19 ` [PATCH 1/1] " Arnd Bergmann
2020-05-07 14:35 ` [GIT PULL] " Christoph Hellwig
2020-05-28 5:46 ` Christoph Hellwig
2020-05-28 5:55 ` John Paul Adrian Glaubitz
2020-05-28 9:40 ` Rob Landley
2020-05-28 16:14 ` Rich Felker
2020-05-28 22:14 ` Rich Felker
2020-05-28 22:28 ` Rob Landley
2020-05-28 22:32 ` John Paul Adrian Glaubitz
2020-05-28 22:37 ` Rich Felker
2020-05-29 14:35 ` Christoph Hellwig
2020-05-29 14:30 ` Christoph Hellwig
2020-05-29 17:53 ` Rich Felker
2020-05-29 18:22 ` Christoph Hellwig
2020-05-30 8:08 ` John Paul Adrian Glaubitz
2020-05-30 8:47 ` Geert Uytterhoeven
2020-05-31 3:20 ` Rob Landley
2020-05-31 8:03 ` John Paul Adrian Glaubitz
2020-06-01 2:55 ` Rich Felker
2020-06-01 8:16 ` John Paul Adrian Glaubitz
2020-06-01 18:13 ` Rich Felker
2020-06-01 21:12 ` Arnd Bergmann
2020-06-02 1:33 ` Rich Felker
2020-06-02 2:49 ` Andrew Morton
2020-06-02 2:53 ` Rich Felker
2020-06-03 7:27 ` John Paul Adrian Glaubitz
2020-06-03 7:31 ` John Paul Adrian Glaubitz
2020-06-05 15:38 ` John Paul Adrian Glaubitz
2020-06-05 15:43 ` Rich Felker
2020-06-05 15:47 ` John Paul Adrian Glaubitz
2020-06-05 15:59 ` Rich Felker
2020-06-05 17:58 ` John Paul Adrian Glaubitz
2020-06-05 18:23 ` Geert Uytterhoeven
2020-06-06 0:50 ` Andrew Morton [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=20200605175030.feba7dc6fc1233b815c72afb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--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