From: Len Brown <lenb@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: sfi-devel@simplefirmware.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: sfi tree build failure
Date: Tue, 07 Jul 2009 11:31:06 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0907071120230.4244@localhost.localdomain> (raw)
In-Reply-To: <20090707154353.628365ac.sfr@canb.auug.org.au>
> I still get the same error.
git.kernel.org took a long time to update from master.kerne.org
last night. (indeed, I was sending patches through e-mail to
some folks to work around it); so I suspect you pulled the SFI
tree before the mirror updated and got the same thing you
got over the weekend.
surfing to git.kernel.org, it seems to be up to date now.
The tree should include this one of interest:
commit 4844be551844e05d4b70f0624e9c34fd486d3e33
Author: Len Brown <len.brown@intel.com>
Date: Mon Jul 6 23:57:55 2009 -0400
SFI: revert changes to linux/acpi.h, fix ppc build
Note that Linus pulls from master.kernel.org rather than git.kernel.org
to avoid any possible sync delay between tree push and his pull.
If you have trouble with a copy of the tree that includes
the commit above, (I don't expect to see the same failure,
but it is always possible there is another one after this one),
then please send me the complete build log.
cheers,
-Len
next prev parent reply other threads:[~2009-07-07 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 7:19 linux-next: sfi tree build failure Stephen Rothwell
2009-07-06 6:14 ` Stephen Rothwell
2009-07-07 4:01 ` Len Brown
2009-07-07 4:13 ` Stephen Rothwell
2009-07-07 5:43 ` Stephen Rothwell
2009-07-07 15:31 ` Len Brown [this message]
2009-07-08 0:50 ` 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=alpine.LFD.2.00.0907071120230.4244@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfi-devel@simplefirmware.org \
--cc=sfr@canb.auug.org.au \
/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