[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111014110425.ce5b966f8f8882114028a23d@canb.auug.org.au>
Date: Fri, 14 Oct 2011 11:04:25 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andi Kleen <andi@...stfloor.org>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Linus <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Please include const-sections into linux-next
Hi Andi,
On Fri, 14 Oct 2011 01:38:18 +0200 Andi Kleen <andi@...stfloor.org> wrote:
>
> 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.
You picked a bad time unfortunately. Today will amost certainly be the
last linux-next tree before the merge window opens (since I will be on
vacation until kernel summit) so if it breaks the tree, it will impact on
others testing (and there won't be a followup tree to correct the problem).
Also, the commit messages are still very terse (as a few people pointed
out) and I have seen no response to Thomas' remarks either.
> 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.
It really isn't trivial because we have had various problems with init
and const in the past with various toolchains (and even different
problems on different architectures with the "same" toolchain).
Linus or Andrew may still want to take these, but I don't think I can add
it to linux-next right now, sorry.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists