Patches added to master & powerpc-next branches of powerpc.git

Patches added to master & powerpc-next branches of powerpc.git

[Paul Mackerras]

I have created a powerpc-next branch in the powerpc.git tree, which
has the following commits on it so far.  The master branch is at the
same point.  I've pulled in Dave Miller's tree (for the LMB changes)
and applied some other patches from the list.

I'm expecting that platform/subarchitecture maintainers will be
sending me pull requests for their trees from time to time.

Paul.

Anton Vorontsov (1):
      [POWERPC] 8xx: Timebase frequency should not depend on bus-frequency

Badari Pulavarty (1):
      [POWERPC] Add code for removing HPTEs for parts of the linear mapping

Becky Bruce (1):
      [LMB]: Make lmb support large physical addressing

Benjamin Herrenschmidt (1):
      [POWERPC] Fix thinko in cpu_thread_mask_to_cores()

Dale Farnsworth (1):
      [POWERPC] Remove dead code at KernelAltiVec

David S. Miller (2):
      [LIB]: Make PowerPC LMB code generic so sparc64 can use it too.
      [LMB]: Fix bug in __lmb_alloc_base().

Johannes Berg (1):
      [POWERPC] mpic: Make sparse happy

Julia Lawall (1):
      [POWERPC] Use FIELD_SIZEOF in arch/ppc

Kumar Gala (2):
      [LMB]: Fix initial lmb add region with a non-zero base
      [LMB]: Fix lmb_add_region if region should be added at the head

Re: Patches added to master & powerpc-next branches of powerpc.git

[Kumar Gala]

On Feb 26, 2008, at 6:03 AM, Paul Mackerras wrote:

> I have created a powerpc-next branch in the powerpc.git tree, which
> has the following commits on it so far.  The master branch is at the
> same point.  I've pulled in Dave Miller's tree (for the LMB changes)
> and applied some other patches from the list.
>
> I'm expecting that platform/subarchitecture maintainers will be
> sending me pull requests for their trees from time to time.
>
> Paul.

How do you plan on managing the powerpc-next branch in the future?   
For example, I assume at some point linus will pull it into what would  
be 2.6.26.  Would you rebase this branch?  etc.

- k

Re: Patches added to master & powerpc-next branches of powerpc.git

[Benjamin Herrenschmidt]

On Tue, 2008-02-26 at 23:03 +1100, Paul Mackerras wrote:
> Benjamin Herrenschmidt (1):
>       [POWERPC] Fix thinko in cpu_thread_mask_to_cores()
> 

Any reason why this isn't going into .25 ?

Ben.

Re: Patches added to master & powerpc-next branches of powerpc.git

[Paul Mackerras]

Benjamin Herrenschmidt writes:

> On Tue, 2008-02-26 at 23:03 +1100, Paul Mackerras wrote:
> > Benjamin Herrenschmidt (1):
> >       [POWERPC] Fix thinko in cpu_thread_mask_to_cores()
> > 
> 
> Any reason why this isn't going into .25 ?

I thought you said nothing uses it.

Paul.

Re: Patches added to master & powerpc-next branches of powerpc.git

[Benjamin Herrenschmidt]

On Wed, 2008-02-27 at 11:43 +1100, Paul Mackerras wrote:
> Benjamin Herrenschmidt writes:
> 
> > On Tue, 2008-02-26 at 23:03 +1100, Paul Mackerras wrote:
> > > Benjamin Herrenschmidt (1):
> > >       [POWERPC] Fix thinko in cpu_thread_mask_to_cores()
> > > 
> > 
> > Any reason why this isn't going into .25 ?
> 
> I thought you said nothing uses it.

I'm worried some out of tree stuff might...

But if not, yeah, it's fine.

Ben.

Re: Patches added to master & powerpc-next branches of powerpc.git

[Paul Mackerras]

Kumar Gala writes:

> How do you plan on managing the powerpc-next branch in the future?   
> For example, I assume at some point linus will pull it into what would  
> be 2.6.26.  Would you rebase this branch?  etc.

Yes, it is basically the for-2.6.26 branch.  I will try very hard not
to rebase it, but I don't promise that I will never rebase it.

I'm expecting to get requests to pull your tree into it, as well as
Josh's, Grant's, etc., once you have stuff that you are reasonably
confident should go in to the next release and won't need to be
rebased.

Paul.