From: Andi Kleen <andi@firstfloor.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Please include const-sections into linux-next
Date: Fri, 14 Oct 2011 01:38:18 +0200 [thread overview]
Message-ID: <20111013233818.GB26654@one.firstfloor.org> (raw)
Stephen,
Please include
git://github.com/andikleen/linux-misc.git const-sections
in linux-next. This has a tree sweep to fix all kind of constant
section issues.
I intend to send Linus a pull request next cycle and would like
to get some testing in next first.
I got various acks last time it was posted and added them all.
In general it falls more in the "trivial" category, but it's
rather large and all over so I may have made a mistake.
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next reply other threads:[~2011-10-13 23:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 23:38 Andi Kleen [this message]
2011-10-14 0:04 ` Stephen Rothwell
2011-10-14 22:26 ` James Bottomley
2011-10-15 22:38 ` [patch] parisc, iommu: add missing include for prefetchw() David Rientjes
2011-10-15 23:48 ` James Bottomley
2011-10-16 0:41 ` David Rientjes
2011-10-16 0:56 ` James Bottomley
2011-10-16 1:15 ` David Rientjes
2011-10-15 23:03 ` Please include const-sections into linux-next David Rientjes
2011-10-15 23:49 ` James Bottomley
2011-10-16 0:53 ` David Rientjes
2011-10-16 0:58 ` James Bottomley
2011-10-16 3:35 ` Andi Kleen
2011-10-16 21:03 ` James Bottomley
2011-10-16 21:57 ` Andi Kleen
2011-10-19 15:54 ` James Bottomley
2011-10-19 16:15 ` Andi Kleen
2011-10-19 16:21 ` James Bottomley
2011-10-19 16:33 ` Andi Kleen
2011-10-19 18:55 ` James Bottomley
2011-10-19 19:05 ` Andi Kleen
2011-10-19 20:04 ` James Bottomley
2011-10-19 20:06 ` James Bottomley
2011-10-19 20:11 ` Andi Kleen
2011-10-19 20:14 ` James Bottomley
2011-10-19 21:24 ` Andi Kleen
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=20111013233818.GB26654@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.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®