linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull from 'next' branch (2.6.29)
Date: Wed, 14 Jan 2009 10:36:38 +1100	[thread overview]
Message-ID: <1231889798.22571.50.camel@pasglop> (raw)
In-Reply-To: <EB245BEE-52C5-40DD-A9DD-A106A5937219@kernel.crashing.org>

On Tue, 2009-01-13 at 15:17 -0600, Kumar Gala wrote:
> On Jan 13, 2009, at 2:59 PM, Benjamin Herrenschmidt wrote:
> 
> > On Tue, 2009-01-13 at 09:21 -0600, Kumar Gala wrote:
> >> Please pull from 'next' branch of
> >>
> >> (this is my last pull request of 'next' for 2.6.29.  I would like  
> >> to see
> >> the 'powerpc: Unify opcode definitions and support' patch go in but  
> >> leave
> >> that for you to pull in directly).
> >
> > This is really very very very late for these changes, most of them
> > aren't bug fixes at all...
> 
> True.
> 
> >> Anton Vorontsov (4):
> >>      powerpc/fsl_pci: Add MPC83xx PCI-E controller RC mode support
> >>      powerpc/83xx: Add PCI-E support for all MPC83xx boards with  
> >> PCI-E
> 
> Would like to see this feature added into .29

Can you either rebase with just that (and bug fixes) ? Or stick that in
another branch ?

> >>      powerpc/83xx: Make serial ports work on MPC8315E-RDB w/ FSL U- 
> >> Boots
> 
> A sort of bug fix.

Ok.

> >>      powerpc/83xx: Move mcu_mpc8349emitx driver out of drivers/i2c/ 
> >> chips/
> 
> At Jean's request to move i2c clients out of drivers/i2c.

Ok.

> >> Kumar Gala (2):
> >>      powerpc/fsl-booke: Cleanup init/exception setup to be runtime
> >>      powerpc/e500mc: Doorbells need to be taken w/exceptions disabled
> 
> can wait for .30

Isn't the second one a clear bug fix ?

> >> Trent Piepho (3):
> >>      powerpc/fsl-booke: Remove code duplication in lowmem mapping
> >>      powerpc/fsl-booke: Allow larger CAM sizes than 256 MB
> >>      powerpc/fsl-booke: Make CAM entries used for lowmem configurable
> 
> Posted we'll before.. finally got around to reviewing them.. but can  
> wait for .30
> 
> So the real question I have is when does your next branch start  
> queuing up changes for .30?

Soon :-)

> I can completely live w/these not going into .29 if they can go into  
> your next branch for .30

Cheers,
Ben.

      parent reply	other threads:[~2009-01-13 23:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 15:21 Please pull from 'next' branch (2.6.29) Kumar Gala
2009-01-13 20:59 ` Benjamin Herrenschmidt
2009-01-13 21:17   ` Kumar Gala
2009-01-13 21:22     ` Kumar Gala
2009-01-13 23:36     ` Benjamin Herrenschmidt [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=1231889798.22571.50.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).