linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "John Rigby" <jrigby@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [Add mpc5121 support PATCHES v3 0/8]
Date: Thu, 17 Jan 2008 17:35:59 -0700	[thread overview]
Message-ID: <fa686aa40801171635m1531ae35t63aac14d6ef46d78@mail.gmail.com> (raw)
In-Reply-To: <1200614738-25654-1-git-send-email-jrigby@freescale.com>

On 1/17/08, John Rigby <jrigby@freescale.com> wrote:
> This is a new improved set of patches based on the
> comments that I received in response to the previous set.
>
> Changes since v2:
>
> 1/8 Add-IPIC-config-option.patch
> 2/8 Add-mpc512x-ipic-support.patch
>     No changes.  These two are in galak's queue for submission.
>
> 3/8 Basic-Freescale-MPC512x-support.patch
>     Added missing of_put_node as pointed out by Stephen Rothwell
>     Added Acked-by: Grant Likely <grant.likely@secretlab.ca>
>
> 4/8 Device-tree-for-MPC5121-ADS.patch
>     Made changes suggested by Grant Likely
>
> 5/8 Separate-MPC52xx-PSC-FIFO-registers-from-rest-of-PSC.patch
> 6/8 Cleanup-checkpatch.pl-problems-in-mpc52xx_uart.c.patch
>     No changes.  Grant is picking up these patches
>
> 7/8 Factor-out-52xx-dependencies-from-52xx-psc-driver.patch
>     No changes.  No comments received.  Too ugly to comment?

No; I'm just percolating on these two.  I'll probably pick these up,
but I need to look at them in greater detail first.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      parent reply	other threads:[~2008-01-18  0:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18  0:05 [Add mpc5121 support PATCHES v3 0/8] John Rigby
2008-01-18  0:05 ` [Add mpc5121 support PATCH v3 1/8] Add IPIC config option John Rigby
2008-01-18  0:05   ` [Add mpc5121 support PATCH v3 2/8] Add mpc512x ipic support John Rigby
2008-01-18  0:05     ` [Add mpc5121 support PATCH v3 3/8] Basic Freescale MPC512x support John Rigby
2008-01-18  0:05       ` [Add mpc5121 support PATCH v3 4/8] Device tree for MPC5121 ADS John Rigby
2008-01-18  0:05         ` [Add mpc5121 support PATCH v3 5/8] Separate MPC52xx PSC FIFO registers from rest of PSC John Rigby
2008-01-18  0:05           ` [Add mpc5121 support PATCH v3 6/8] Cleanup checkpatch.pl problems in mpc52xx_uart.c John Rigby
2008-01-18  0:05             ` [Add mpc5121 support PATCH v3 7/8] Factor out 52xx dependencies from 52xx psc driver John Rigby
2008-01-18  0:05               ` [Add mpc5121 support PATCH v3 8/8] Add MPC512x support to MPC52xx " John Rigby
2008-01-19  6:58               ` [Add mpc5121 support PATCH v3 7/8] Factor out 52xx dependencies from 52xx " Grant Likely
2008-01-19  6:59                 ` Grant Likely
2008-01-20  3:33                   ` John Rigby
2008-01-18  6:51     ` [Add mpc5121 support PATCH v3 2/8] Add mpc512x ipic support Kumar Gala
2008-01-18  6:50   ` [Add mpc5121 support PATCH v3 1/8] Add IPIC config option Kumar Gala
2008-01-18  0:35 ` Grant Likely [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=fa686aa40801171635m1531ae35t63aac14d6ef46d78@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jrigby@freescale.com \
    --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).