From: Josh Poimboeuf <jpoimboe@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
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 23:28:40 -0500 [thread overview]
Message-ID: <20160804042840.k355wibzjp5yikxb@treble> (raw)
In-Reply-To: <CAB=NE6VpHJLicvrKhPhQD4p+hNRCpvPJU7AXFAQdxXeDWfPLJQ@mail.gmail.com>
On Wed, Aug 03, 2016 at 12:56:22PM -0700, 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 ?
>
> So is this OK to merge into my series into the patch "sections.h: add
> sections header to collect all section info".
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 49b354cb455a..9919277c66ae 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5190,6 +5190,18 @@ S: Supported
> F: drivers/base/power/domain*.c
> F: include/linux/pm_domain.h
>
> +GENERIC SECTIONS
> +M: "Luis R. Rodriguez" <mcgrof@kernel.org>
> +M: Josh Poimboeuf <jpoimboe@redhat.com>
> +M: Arnd Bergmann <arnd@arndb.de>
> +L: linux-arch@vger.kernel.org
> +L: linux-kernel@vger.kernel.org
> +S: Supported
> +F: include/asm-generic/section-core.h
> +F: include/asm-generic/sections.h
> +F: include/asm-generic/vmlinux.lds.h
> +F: Documentation/DocBook/sections.tmpl
Hi Luis,
Thanks to my past work with objtool and kpatch, I know far more than I
ever wanted to know about all the kernel's custom ELF sections. So it's
fine with me if you want to add me as a maintainer for those files.
--
Josh
next prev parent reply other threads:[~2016-08-04 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 19:56 Luis R. Rodriguez
2016-08-03 20:11 ` Arnd Bergmann
2016-08-03 20:25 ` Luis R. Rodriguez
2016-08-04 4:28 ` Josh Poimboeuf [this message]
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=20160804042840.k355wibzjp5yikxb@treble \
--to=jpoimboe@redhat.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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
all inboxes | Powered by JetHome®