From: Andi Kleen <ak@suse.de>
To: vgoyal@in.ibm.com
Cc: Alon Bar-Lev <alon.barlev@gmail.com>,
Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20 -- Loads of section mismatches
Date: 05 Feb 2007 11:48:57 +0100 [thread overview]
Message-ID: <p73sldknali.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070205064029.GA23996@in.ibm.com>
Vivek Goyal <vgoyal@in.ibm.com> writes:
>
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/broken-out/x86_64-mm-move-startup_32-in-texthead-section.patch
>
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/broken-out/x86_64-mm-break-init-in-two-parts-to-avoid-modpost-warnings.patch
The two part init / head.S patch was considered too intrusive late
in the game.
Near all of the other section patches should have made it in though.
-Andi
next prev parent reply other threads:[~2007-02-05 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 22:02 2.6.20 -- Loads of section mismatches Miles Lane
2007-02-04 22:06 ` Alon Bar-Lev
2007-02-05 6:40 ` Vivek Goyal
2007-02-05 10:48 ` Andi Kleen [this message]
2007-02-06 10:27 ` Vivek Goyal
2007-02-06 18:09 ` Andrew Morton
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=p73sldknali.fsf@bingen.suse.de \
--to=ak@suse.de \
--cc=alon.barlev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=vgoyal@in.ibm.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