LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: linuxppc-dev@ozlabs.org, Gala Kumar <kumar.gala@freescale.com>
Subject: Re: Status of fsl booke TLB and ATMU patches
Date: Sat, 03 Jan 2009 16:30:30 +1100	[thread overview]
Message-ID: <1230960630.15389.102.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.58.0901021611260.25853@shell2.speakeasy.net>

On Fri, 2009-01-02 at 16:18 -0800, Trent Piepho wrote:
> 2.6.28 is out, can my existing patches be accepted?

It's all FSL stuff and thus in Kumar's hands. I think there's a pending
pull request from him tho, thus maybe they are in there already :-)

I've just officially taken over so I'll scrub patchwork and outstanding
sub maintainer pull requests if any early next week.

Cheers,
Ben.

> [2/2] POWERPC/fsl-pci: Set relaxed ordering on prefetchable ranges
> http://patchwork.ozlabs.org/patch/14546/
> 
> [1/2] POWERPC/fsl-pci: Better ATMU setup
> http://patchwork.ozlabs.org/patch/14544/
> 
> [5/5] powerpc: booke: Allow larger CAM sizes than 256 MB
> http://patchwork.ozlabs.org/patch/12885/
> 
> [4/5] powerpc: booke: Make CAM entries used for lowmem configurable
> http://patchwork.ozlabs.org/patch/12884/
> 
> [3/5] powerpc: booke: Remove code duplication in lowmem mapping
> http://patchwork.ozlabs.org/patch/12883/
> 
> [2/5] powerpc: booke: Remove num_tlbcam_entries
> http://patchwork.ozlabs.org/patch/12882/
> 
> [1/5] powerpc: booke: Don't hard-code size of struct tlbcam
> http://patchwork.ozlabs.org/patch/12881/
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev

  reply	other threads:[~2009-01-03  5:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03  0:18 Status of fsl booke TLB and ATMU patches Trent Piepho
2009-01-03  5:30 ` Benjamin Herrenschmidt [this message]
2009-01-03 19:32   ` Kumar Gala

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=1230960630.15389.102.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=xyzzy@speakeasy.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