public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: sfi-devel@simplefirmware.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: sfi tree build failure
Date: Wed, 8 Jul 2009 10:50:05 +1000	[thread overview]
Message-ID: <20090708105005.3d8facaa.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0907071120230.4244@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]

Hi Len,

On Tue, 07 Jul 2009 11:31:06 -0400 (EDT) Len Brown <lenb@kernel.org> wrote:
>
> > 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.

I fetch from master ... and did get an update.

> 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

It has that now.  When I refetched yesterday, the head of sfi-test branch
was c24b5f47a66895c2f2ac6e8b665c94f7854e32b4 ("SFI: work around ppc build
failure") which is the commit before the above one.

It doesn't matter, hopefully it will be better today.

> 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.

As do I for the same reason.

> 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.

Will do.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-07-08  0:50 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
2009-07-08  0:50         ` 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=20090708105005.3d8facaa.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=lenb@kernel.org \
    --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