From: Sam Ravnborg <sam@ravnborg.org>
To: Geoff Levand <geoff@infradead.org>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/1] vmlinux.lds.h: Add new SECTION() macro
Date: Fri, 16 May 2014 12:12:04 +0200 [thread overview]
Message-ID: <20140516101204.GA10187@ravnborg.org> (raw)
In-Reply-To: <1400189158.11178.157.camel@smoke>
On Thu, May 15, 2014 at 02:25:58PM -0700, Geoff Levand wrote:
> Add a new preprocessor macro SECTION() to vmlinux.lds.h that defines a
> linker script output section with the section attributes commonly used,
> and replace all occurrences of equivalent descriptions in vmlinux.lds.h
> with the new macro.
Looks good - but the name is too generic.
Use OUTPUT_SECTION() as you suggest in the comment below.
If you walk through all linker scripts then keep an eay out for
stuff where the generic stuff can be used.
And see if there is something else that really belongs in asm-generic.
Sam
prev parent reply other threads:[~2014-05-16 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 21:25 [RFC 1/1] vmlinux.lds.h: Add new SECTION() macro Geoff Levand
2014-05-16 10:12 ` Sam Ravnborg [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=20140516101204.GA10187@ravnborg.org \
--to=sam@ravnborg.org \
--cc=geoff@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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