From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Abbott <tabbott@MIT.EDU>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Anders Kaseorg <andersk@MIT.EDU>, Waseem Daher <wdaher@MIT.EDU>,
Denys Vlasenko <vda.linux@googlemail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Andi Kleen <andi@firstfloor.org>, Jeff Arnold <jbarnold@MIT.EDU>
Subject: Re: [PATCH 0/4] Add support for compiling with -ffunction-sections -fdata-sections
Date: Tue, 24 Mar 2009 07:46:37 -0700 [thread overview]
Message-ID: <49C8F24D.6000603@zytor.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0903240210410.21037@vinegar-pot.mit.edu>
Tim Abbott wrote:
>
> Yeah, unfortunately, because people are always modifying the kernel's
> "magic" sections, a version of the patch that applies to master will
> basically always conflict with something in linux-next (at least, this has
> been my experience updating it during the 2.6.29 release cycle). As Rusty
> Russell said last month about this patch, there's no good time for this
> kind of change.
>
"Just before -rc1" is pretty much the only time to do this kind of
changes. It's not the first time we have had this issue.
-hpa
next prev parent reply other threads:[~2009-03-24 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 5:28 [PATCH 0/4] Add support for compiling with -ffunction-sections -fdata-sections Tim Abbott
2009-03-24 5:28 ` [PATCH 1/4] Make section names compatible " Tim Abbott
2009-03-24 5:28 ` [PATCH 2/4] modpost: Check the section flags, not name, to catch missing "ax"/"aw" Tim Abbott
2009-03-24 5:28 ` [PATCH 3/4] modpost: Support objects with more than 64k sections Tim Abbott
2009-03-24 5:28 ` [PATCH 4/4] x86: Add an option to compile with -ffunction-sections -fdata-sections Tim Abbott
2009-03-24 6:07 ` [PATCH 0/4] Add support for compiling " Stephen Rothwell
2009-03-24 7:23 ` Tim Abbott
2009-03-24 14:46 ` H. Peter Anvin [this message]
2009-03-27 1:41 ` Tim Abbott
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=49C8F24D.6000603@zytor.com \
--to=hpa@zytor.com \
--cc=andersk@MIT.EDU \
--cc=andi@firstfloor.org \
--cc=jbarnold@MIT.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=tabbott@MIT.EDU \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
--cc=wdaher@MIT.EDU \
/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