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, hpa@zytor.com,
	linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: Fix build with older binutils and consolidate linker script
Date: Tue, 25 Aug 2009 15:56:51 +0200	[thread overview]
Message-ID: <20090825135651.GA22484@elte.hu> (raw)
In-Reply-To: <4A9408FC02000078000119B1@vpn.id2.novell.com>


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

> >>> Ingo Molnar <mingo@elte.hu> 25.08.09 09:50 >>>
> >
> >* tip-bot for Jan Beulich <JBeulich@novell.com> wrote:
> >
> >> Commit-ID:  ddc98b38b6320d5de2e3167673a06ec1a48e9d0e
> >> Gitweb:     http://git.kernel.org/tip/ddc98b38b6320d5de2e3167673a06ec1a48e9d0e 
> >> Author:     Jan Beulich <JBeulich@novell.com>
> >> AuthorDate: Tue, 18 Aug 2009 16:51:27 +0100
> >> Committer:  H. Peter Anvin <hpa@zytor.com>
> >> CommitDate: Mon, 24 Aug 2009 15:51:35 -0700
> >> 
> >> x86: Fix build with older binutils and consolidate linker script
> >
> >this breaks the build with newer binutils:
> 
> With the updated patch just submitted I made sure UP and SMP 
> builds work as well as building with old and current binutils. 

Thanks, applied.

> Sorry for having forgotten to do so before submitting the first 
> time (I know I had intended to).

This happens. I'm still unsure whether we can do it in .31.0 or need 
to delay it to .31.1 via a -stable backport tag. One more problem 
with it and i think we'll need to delay it - it's just too large and 
changes too many aspects of the linker script.

Would it be possible to split it into two pieces: 'minimal fix' and 
'clean up' portions?

	Ingo

  reply	other threads:[~2009-08-25 13:57 UTC|newest]

Thread overview: 17+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2009-08-25 13:50 [PATCH] x86: fix build with older binutils and consolidate linker script (v2) Jan Beulich
2009-08-25 14:01 ` [tip:x86/urgent] x86: Fix build with older binutils and consolidate linker script tip-bot for Jan Beulich

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=20090825135651.GA22484@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