From: Andrew Morton <akpm@linux-foundation.org>
To: Mathias Krause <minipli@googlemail.com>
Cc: Joe Perches <joe@perches.com>, Mason <slash.tmp@free.fr>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: String literals in __init functions
Date: Thu, 26 Mar 2015 14:40:58 -0700 [thread overview]
Message-ID: <20150326144058.56ef6916b00ad38030296089@linux-foundation.org> (raw)
In-Reply-To: <CA+rthh8irf+tTSbomivu=bgN-L1k99TQ-q6UYgmMRC1PNOG7qw@mail.gmail.com>
On Thu, 26 Mar 2015 21:49:06 +0100 Mathias Krause <minipli@googlemail.com> wrote:
> Andrew, what's your opinion on such a patch set? Do you too think it's
> useful? Or do you share Ingo's fear about the additional maintenance
> burden?
I don't think the burden would be toooo high, although it will mess the
code up a bit.
The post-build checking for section reference mismatches will help,
although that seems to have got itself turned off (what happened
there?).
Did anyone look at writing a postprocessor for the .s files? It
doesn't look like it will be too hard from an initial peek.
Did anyone ask the gcc developers? I'd have thought that a function-wide
__attribute__((__string_section__(foo))
wouldn't be a ton of work to implement.
next prev parent reply other threads:[~2015-03-26 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 17:56 Mason
2015-03-25 18:01 ` Joe Perches
2015-03-26 12:40 ` Mason
2015-03-26 16:13 ` Joe Perches
2015-03-26 16:37 ` Mathias Krause
2015-03-26 17:53 ` Joe Perches
2015-03-26 20:49 ` Mathias Krause
2015-03-26 21:40 ` Andrew Morton [this message]
2015-03-26 21:58 ` Joe Perches
2015-03-26 22:15 ` Andrew Morton
2015-03-27 7:16 ` Mathias Krause
2015-04-02 16:00 ` Joseph Myers
2015-04-02 16:23 ` Joe Perches
2015-03-27 7:05 ` Mathias Krause
2015-03-27 7:32 ` Joe Perches
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=20150326144058.56ef6916b00ad38030296089@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=minipli@googlemail.com \
--cc=slash.tmp@free.fr \
/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®