linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCHv3 1/2] [POWERPC] CPM2: Implement GPIO LIB API on CPM2 Freescale SoC.
Date: Fri, 18 Jul 2008 17:07:56 +0200	[thread overview]
Message-ID: <200807181707.56921.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <97D0950D-BBCA-4859-936E-774D887B05DC@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

On Friday 18 July 2008, Kumar Gala wrote:
> 
> On Jul 18, 2008, at 9:38 AM, Laurent Pinchart wrote:
> 
> > On Friday 27 June 2008, Jochen Friedrich wrote:
> >> Hi Laurent,
> >>
> >>> Is there any pending issue or can this be applied to powerpc-next ?
> >>
> >> Looks OK to me.
> >>
> >>>> Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
> >>>> Cc: Jochen Friedrich <jochen@scram.de>
> >> Acked-by: Jochen Friedrich <jochen@scram.de>
> >
> > Any news on this patch ? Kumar, could you apply it to your tree for  
> > 2.6.27 ?
> 
> Can you repost it.  I not sure what patch 2/2 was and if I've already  
> dealt with it.

2/2 was "[PATCH2/2] [POWERPC] CPM1: implement GPIO LIB API on CPM1 Freescale SoC." posted by Jochen Friedrich. You haven't dealt with it yet as far as I know, but it would be up to Jochen to resubmit.

The "PATCHv3 1/2" patch can be considered as-is, as it doesn't depend on 2/2. Should I resubmit a "PATCHv4" that just changes the subject line ?

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-07-18 15:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 17:16 [PATCHv2 1/2] [POWERPC] CPM2: Implement GPIO LIB API on CPM2 Freescale SoC Jochen Friedrich
2008-06-13 12:46 ` Laurent Pinchart
2008-06-13 14:57   ` Anton Vorontsov
2008-06-13 15:15     ` Laurent Pinchart
2008-06-18 16:56       ` Jochen Friedrich
2008-06-18 17:08         ` [PATCHv3 " Laurent Pinchart
2008-06-26 11:14           ` Laurent Pinchart
2008-06-27 16:50             ` Jochen Friedrich
2008-07-18 14:38               ` Laurent Pinchart
2008-07-18 14:50                 ` Kumar Gala
2008-07-18 15:07                   ` Laurent Pinchart [this message]
2008-07-18 15:28                     ` Kumar Gala
2008-07-18 15:28           ` Kumar Gala
2008-07-18 15:30             ` Jochen Friedrich
2008-07-18 15:46               ` Kumar Gala
2008-07-18 15:52                 ` Jochen Friedrich
2008-07-24 14:46                 ` Laurent Pinchart
2008-07-24 15:12                   ` Kumar Gala
2008-07-24 16:00                     ` [PATCHv4] cpm2: " Laurent Pinchart
2008-07-25 17:42                       ` Kumar Gala
2008-07-28  8:43                         ` Laurent Pinchart
2008-07-28 12:42                           ` 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=200807181707.56921.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).