public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: Re: "next" branch update
Date: Tue, 02 Jun 2009 13:44:23 +1000	[thread overview]
Message-ID: <1243914263.5308.16.camel@pasglop> (raw)
In-Reply-To: <fa686aa40906012026r71b3b75ar13790f7a569d9c08@mail.gmail.com>

On Mon, 2009-06-01 at 21:26 -0600, Grant Likely wrote:
> How about the iomap_early() patch?  What would you like me to do with
> that one?

Wait for me to review it :-)

Cheers,
Ben.

> g.
> 
> > On Jun 1, 2009 9:04 PM, "Benjamin Herrenschmidt"
> > <benh@kernel•crashing.org> wrote:
> > 
> > I've updated powerpc "next branch" with the following patches:
> > 
> > (Kumar: The swiotlb patch is still segregated in "test" until we
> > resolve
> > how it's going to be merged vs. Ian Campbell series).
> > 
> > Anton Blanchard (1):
> >      powerpc: Convert RTAS event scan from kernel thread to
> > workqueue
> > 
> > Michael Ellerman (3):
> >      powerpc/ftrace: Use ppc_function_entry() instead of GET_ADDR
> >      powerpc/ftrace: Remove unused macros
> >      powerpc/ftrace: Use PPC_INST_NOP directly
> > 
> > Michael Neuling (1):
> >      powerpc: Make the NR_CPUS max 8192
> > 
> > Michel Dänzer (1):
> >      therm_adt746x: Always clear hardware bit which inverts fan
> > speed range.
> > 
> > Nathan Fontenot (1):
> >      powerpc: Display processor virtualization resource allocs in
> > lparcfg
> > 
> > Stephen Rothwell (1):
> >      powerpc/pci: Fix annotation of pcibios_claim_one_bus
> > 
> > roel kluin (1):
> >      tape: beyond ARRAY_SIZE of viocd_diskinfo
> > 
> > 
> > 
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev@ozlabs•org
> > https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 

  reply	other threads:[~2009-06-02  3:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02  3:03 "next" branch update Benjamin Herrenschmidt
2009-06-02  3:26 ` Grant Likely
2009-06-02  3:44   ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-10  3:14 Benjamin Herrenschmidt
2009-06-10  4:13 ` Grant Likely
2009-06-10  6:07 ` Timur Tabi
2009-06-11 17:05 ` Josh Boyer
2009-06-12  7:29 Benjamin Herrenschmidt
2009-06-12 13:54 ` Timur Tabi
2009-06-12 13:59   ` Benjamin Herrenschmidt
2009-07-28  4:14 Benjamin Herrenschmidt
2009-07-28  7:54 ` Martyn Welch

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=1243914263.5308.16.camel@pasglop \
    --to=benh@kernel$(echo .)crashing.org \
    --cc=grant.likely@secretlab$(echo .)ca \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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