From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Joe Perches <joe@perches.com>
Subject: Re: Generic section maintainers
Date: Wed, 3 Aug 2016 22:25:13 +0200 [thread overview]
Message-ID: <20160803202513.GU3296@wotan.suse.de> (raw)
In-Reply-To: <4940990.NJeuzLZEL9@wuerfel>
On Wed, Aug 03, 2016 at 10:11:48PM +0200, Arnd Bergmann wrote:
> On Wednesday, August 3, 2016 12:56:22 PM CEST Luis R. Rodriguez wrote:
> > Arnd, Josh,
> >
> > In my linker table work [0], other than the linker table work and
> > section ranges stuff, I'm adding:
> >
> > o include/linux/sections.h
> > o include/asm-generic/section-core.h (not in RFC v3 but it is in my
> > RFC v4 series not yet posted, splitting this up fixes compilation on
> > powerpc which otherwise creates a header issue nightmare to resolve)
> >
> > I extend include/asm-generic/sections.h to then include
> > <asm-generic/section-core.h>, and furthermore provide the beginning of
> > a central place to document in a central place all common sections.
> >
> > As per checkpatch complaints I'll be adding myself to MAINTAINERS for
> > the linker table headers, section ranges, but noticed then we don't
> > have anyone in particularly looking carefully after
> > include/asm-generic/sections.h other than the default which is Arnd.
> > Given this work on streamlining the section stuff, I'd like to help so
> > am considering adding a specific entry on MAINTAINRERS for generic
> > sections and adding myself to it along with Arnd. Wanted to check if
> > this is OK. While at it, it occurred to me that you might be
> > interested in this a swell Josh, given your work with objtool. Would
> > anyone else like to help with active maintenance / review of these ?
>
> I'd rather not be listed separately for this file, I'm not really
> an expert on linker scripts, and checkpatch.pl will pick up my
> address anyway.
I'm definitely not an expert on linker scripts, nor do I think many folk are, I
just need to get work done and by chance have gotten involved into dark creepy
corners.
> With my name removed from the entry, please add
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
OK I'll fold the changes into the patch provided Josh is also OK
with it, but will keep the ACK out given that the patch has other
changes, I'd hope for a review upon the next respin.
> If you want, I can still merge the patches for these files through
> my asm-generic git tree, but then I'd rely on you to pick them
> up and forward them after review.
Sure.
Luis
next prev parent reply other threads:[~2016-08-03 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 19:56 Generic section maintainers Luis R. Rodriguez
2016-08-03 20:11 ` Arnd Bergmann
2016-08-03 20:25 ` Luis R. Rodriguez [this message]
2016-08-04 4:28 ` Josh Poimboeuf
2016-08-04 17:06 ` Luis R. Rodriguez
2016-08-04 18:47 ` H. Peter Anvin
2016-08-04 19:11 ` Luis R. Rodriguez
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=20160803202513.GU3296@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=jpoimboe@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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