From: Nicholas Piggin <npiggin@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Michael Matz <matz@suse.de>,
Arnd Bergmann <arnd@arndb.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kees Cook <keescook@chromium.org>,
Guenter Roeck <linux@roeck-us.net>,
Masami Hiramatsu <mhiramat@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Wang Nan <wangnan0@huawei.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Borislav Petkov <bp@alien8.de>, Joerg Roedel <joro@8bytes.org>
Subject: Re: linker-tables v5 testing
Date: Thu, 1 Dec 2016 16:20:39 +1100 [thread overview]
Message-ID: <20161201162039.602da20a@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20161201160430.6e95710a@roar.ozlabs.ibm.com>
On Thu, 1 Dec 2016 16:04:30 +1100
Nicholas Piggin <npiggin@gmail.com> wrote:
> On Wed, 30 Nov 2016 19:15:27 -0800
> "Luis R. Rodriguez" <mcgrof@kernel.org> wrote:
>
> > On Wed, Nov 30, 2016 at 6:51 PM, Nicholas Piggin <npiggin@gmail.com> wrote:
> > > On Wed, 30 Nov 2016 18:38:16 +0100
> > > "Luis R. Rodriguez" <mcgrof@kernel.org> wrote:
> > >
> > >> On Wed, Nov 30, 2016 at 02:09:47PM +1100, Nicholas Piggin wrote:
>
> > >> What is wrong with that ? Separating linker table and section ranges is
> > >
> > > It's not that you separate those, of course you need that. It's that
> > > you also separate other sections from the input section descriptions:
> > >
> > > - *(.text.hot .text .text.fixup .text.unlikely) \
> > > + *(.text.hot .text) \
> > > + *(SORT(.text.rng.*)) \
> > > + *(.text.fixup .text.unlikely) \
Ahh, you're doing it to avoid clash with compiler generated sections.
The usual way to cope with that seems to be to use two dots for your name.
.text..rng.*
next prev parent reply other threads:[~2016-12-01 5:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 4:11 Luis R. Rodriguez
2016-11-24 4:57 ` Guenter Roeck
2016-11-24 16:18 ` Guenter Roeck
2016-11-30 1:33 ` Luis R. Rodriguez
2016-11-30 3:09 ` Nicholas Piggin
2016-11-30 17:38 ` Luis R. Rodriguez
2016-12-01 2:51 ` Nicholas Piggin
2016-12-01 3:15 ` Luis R. Rodriguez
2016-12-01 5:04 ` Nicholas Piggin
2016-12-01 5:20 ` Nicholas Piggin [this message]
2016-12-01 16:34 ` Luis R. Rodriguez
[not found] ` <CANashXMF3jWNgxaSQLRg2b88fSo1xEw-CDFQ6D94eoNn=mYuHQ@mail.gmail.com>
[not found] ` <CANashXOkLvy6BHupz8r-yNvihbohoXdrSQ38uq3jg2q3bGjX_w@mail.gmail.com>
[not found] ` <CANashXOb2jGtXr3BmxVKERPDp-DAHtZXYneZDEf07YpMmoqb-w@mail.gmail.com>
2016-12-02 15:49 ` Luis R. Rodriguez
2016-12-09 2:11 ` Nicholas Piggin
2016-12-02 20:20 ` Luis R. Rodriguez
2016-11-30 4:17 ` Guenter Roeck
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=20161201162039.602da20a@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=joro@8bytes.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matz@suse.de \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.com \
/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®