public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <JBeulich@novell.com>
Cc: tglx@linutronix.de, mingo@redhat.com,
	linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	hpa@zytor.com
Subject: Re: [tip:x86/urgent] x86: Fix build with older binutilsandconsolidate linker script
Date: Tue, 25 Aug 2009 16:48:16 +0200	[thread overview]
Message-ID: <20090825144816.GA28026@elte.hu> (raw)
In-Reply-To: <4A9412DE0200007800011A07@vpn.id2.novell.com>


* Jan Beulich <JBeulich@novell.com> wrote:

> >>> Ingo Molnar <mingo@elte.hu> 25.08.09 16:14 >>>
> >
> >* Jan Beulich <JBeulich@novell.com> wrote:
> >
> >> >>> Ingo Molnar <mingo@elte.hu> 25.08.09 15:56 >>>
> >> >Would it be possible to split it into two pieces: 'minimal fix' and 
> >> >'clean up' portions?
> >> 
> >> Besides being cumbersome, that would make it even larger, so I'd 
> >> say that's not worth it.
> >
> >I mean the two patches yield the same end result. The first one 
> 
> I also understood it that way.
> 
> >(which is smaller, hopefully) gets committed to x86/urgent, the 
> >second one (the cleanups and other non-essentials) gets pushed 
> >upstream in .32.
> 
> The cleanup part really isn't much more than what I described with 
> "Once touching this code, also use the various data section helper 
> macros from include/asm-generic/vmlinux.lds.h.", and if the first 
> patch wouldn't use those macros, it would just grow and become 
> even less readable.

fair enough. Lets hope it all goes fine.

	Ingo

      reply	other threads:[~2009-08-25 14:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 15:51 [PATCH] x86: fix build with older binutils and consolidate linker script Jan Beulich
2009-08-21 20:23 ` H. Peter Anvin
2009-08-24  6:55   ` Jan Beulich
2009-08-24  7:13     ` H. Peter Anvin
2009-08-24  7:21       ` Jan Beulich
2009-08-24 16:09         ` H. Peter Anvin
2009-08-24 22:55 ` [tip:x86/urgent] x86: Fix " tip-bot for Jan Beulich
2009-08-25  7:50   ` Ingo Molnar
2009-08-25  8:01     ` Jan Beulich
2009-08-25  8:27       ` Ingo Molnar
2009-08-25 13:53     ` Jan Beulich
2009-08-25 13:56       ` Ingo Molnar
2009-08-25 14:01         ` [tip:x86/urgent] x86: Fix build with older binutils andconsolidate " Jan Beulich
2009-08-25 14:14           ` Ingo Molnar
2009-08-25 14:35             ` [tip:x86/urgent] x86: Fix build with older binutilsandconsolidate " Jan Beulich
2009-08-25 14:48               ` Ingo Molnar [this message]

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=20090825144816.GA28026@elte.hu \
    --to=mingo@elte.hu \
    --cc=JBeulich@novell.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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