From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: voyager tree build failure
Date: Wed, 10 Jun 2009 02:06:04 +1000 [thread overview]
Message-ID: <20090610020604.fb2b47f3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1244560718.4137.26.camel@mulgrave.site>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hi James,
On Tue, 09 Jun 2009 10:18:38 -0500 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
> Thanks for finding this. The fix looks to be a dummy definition of this
> function for x86_64. The final fix (which has been under discussion)
> will be the elimination of safe_smp_processor_id() altogether.
>
> I've merged this into the
>
> [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops
>
> patch and respun the tree (and built it with an x86-64 cross compiler),
> so it should be safe to include next time around
Thanks. We will see how we do (later) in the morning.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-06-09 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 9:40 linux-next: voyager tree build failure Stephen Rothwell
2009-06-09 15:18 ` James Bottomley
2009-06-09 16:06 ` Stephen Rothwell [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=20090610020604.fb2b47f3.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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