Subject: Re: linux-next: manual merge of the acpi tree

From: Ingo Molnar <[email-masked]>
Date: Fri, 27 Jun 2008 09:17:01 +0200

* Len Brown <[email-masked]> wrote:

> 
> 
> > I was thinking about these:
> > 
> >  acpi-acpi_numa_init-build-fix
> >  ia64, acpi: fix Altix boot breakage in ACPI
> >  acpi: fix boot breakage on Altix
> > 
> > note that this build failure does _not_ occur with current mainline, so 
> > it's a linux-next issue.
> > 
> > i've prepared a tip/acpi-for-len branch for you so that you can have a 
> > look at these, you can pull them from:
> > 
> >    git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git acpi-for-len
> 
> I can see these on the web, but i've got no idea how to traverse your 
> tip tree by actually pulling it.  It seems to be a maze of branches, 
> and it isn't clear how to find the one i want.

the thing you want to look at this is to use the URI above:

   git-pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git acpi-for-len

it's based on -git, so it pulls in no other unrelated changes.

> are the 2nd and 3rd patches in response to the 1st patch? is the 1st 
> patch fixing something that happens in real life, or a random build 
> failuire that only a computer can find?

the build failure happens on allyesconfig as well. (but obviously we 
want to fix 'random' failures just as much - even if most users would be 
unlikely to find a particular config combination - to make the kernel 
more testable.)

	Ingo