lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 8 Jul 2009 10:50:05 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Len Brown <lenb@...nel.org>
Cc:	sfi-devel@...plefirmware.org, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: sfi tree build failure

Hi Len,

On Tue, 07 Jul 2009 11:31:06 -0400 (EDT) Len Brown <lenb@...nel.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@...el.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@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ