linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Rigby" <jcrigby@gmail.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: patches for 2.6.27...
Date: Mon, 7 Jul 2008 07:45:12 -0600	[thread overview]
Message-ID: <4b73d43f0807070645n7fac5b71tdb2fff286e1e5a8a@mail.gmail.com> (raw)
In-Reply-To: <068935A1-11BE-4AEB-9C0E-E1AB53F1618E@kernel.crashing.org>

Two pci patches that are prereq's for 5121 pci:


http://patchwork.ozlabs.org/linuxppc/patch?person=518&id=19299
http://patchwork.ozlabs.org/linuxppc/patch?person=518&id=19300

On Wed, Jul 2, 2008 at 1:56 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
> Please point out any patches that have been posted but havent made it into a
> git tree related to Freescale chips.
>
> I know there are probably a slew of CPM patches that need to get into the
> tree.
>
> - k
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>

      parent reply	other threads:[~2008-07-07 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02  7:56 patches for 2.6.27 Kumar Gala
2008-07-02  8:36 ` Laurent Pinchart
2008-07-06 14:54   ` Vitaly Bordug
2008-07-02 15:41 ` Scott Wood
2008-07-02 15:59 ` Kim Phillips
2008-07-04 22:33   ` Segher Boessenkool
2008-07-02 17:25 ` Dave Jiang
     [not found] ` <200807021214.58080.pterry@vmetro.com>
2008-07-02 19:52   ` Kumar Gala
2008-07-03 15:59 ` Anton Vorontsov
2008-07-07 13:45 ` John Rigby [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=4b73d43f0807070645n7fac5b71tdb2fff286e1e5a8a@mail.gmail.com \
    --to=jcrigby@gmail.com \
    --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).