From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Feng Tang <feng.tang@intel.com>
Cc: "sfi-devel@simplefirmware.org" <sfi-devel@simplefirmware.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [SFI-devel] linux-next: sfi tree build warning
Date: Wed, 8 Jul 2009 17:40:47 +1000 [thread overview]
Message-ID: <20090708174047.c8abca80.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090708145740.0e5e4b07@feng-desktop>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Hi Feng,
On Wed, 8 Jul 2009 14:57:40 +0800 Feng Tang <feng.tang@intel.com> wrote:
>
> Thanks for the finding. Could you help to test the following quick patch?
> it should works for both x86_32 and x86_64. thanks
That patch makes the warning go away for an x86_84 allmodconfig build.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-08 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 6:44 linux-next: sfi tree build warning Stephen Rothwell
2009-07-08 6:57 ` [SFI-devel] " Feng Tang
2009-07-08 7:40 ` Stephen Rothwell [this message]
2009-07-08 15:26 ` Len Brown
2009-07-08 23:45 ` Stephen Rothwell
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=20090708174047.c8abca80.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfi-devel@simplefirmware.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