public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: davem@davemloft.net, Ingo Molnar <mingo@kernel.org>,
	tglx@linutronix.de, dborkman@redhat.com, ffusco@redhat.com,
	tgraf@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] x86/hash: fix build failure with older binutils
Date: Mon, 24 Feb 2014 03:57:12 -0800	[thread overview]
Message-ID: <530B3398.5080308@zytor.com> (raw)
In-Reply-To: <530B0948020000780011E968@nat28.tlf.novell.com>

On 02/23/2014 11:56 PM, Jan Beulich wrote:
>
> 2.17 doesn't have support for it either, yet has support for fxsaveq
> (which you can see in the patch context we check for too). Apart
> from that Documentation/Changes continues to state binutils 2.12
> to be the minimum requirement...
>

Documentation/Changes (maybe) reflects the minimums across all 
architectures, which really has never applied to any single architecture 
for a long time.  x86 requires gcc 3.4 at a minimum, for example, and it 
is not clear that that is sufficient anymore, either.

We don't really have good documentation about what the requirements for 
various specific arches are...

That being said, it sounds like this one is justified.

	-hpa



      reply	other threads:[~2014-02-24 11:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 10:32 [PATCH 1/3] x86/hash: fix build failure with older binutils Jan Beulich
2014-02-21 12:51 ` H. Peter Anvin
2014-02-21 14:16   ` Jan Beulich
2014-02-21 19:17     ` H. Peter Anvin
2014-02-24  7:56       ` Jan Beulich
2014-02-24 11:57         ` H. Peter Anvin [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=530B3398.5080308@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=ffusco@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tgraf@redhat.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