All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH v3 0/5] Renesas TPU PWM support
Date: Thu, 13 Jun 2013 15:38:51 +0000	[thread overview]
Message-ID: <4097084.Y91d0ZYkWB@avalon> (raw)
In-Reply-To: <20130612101250.GB30841@mithrandir>

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

Hi Thierry,

On Wednesday 12 June 2013 12:12:51 Thierry Reding wrote:
> On Tue, Jun 11, 2013 at 03:45:39PM +0200, Laurent Pinchart wrote:
> [...]
> 
> > I believe I've addressed most comments received in response to v2, with
> > the exception of channel allocation at .request() time for which I haven't
> > received any answer to my questions. That will hopefully not be a
> > showstopper.
>
> I totally forgot to reply to that mail. Done now. Irrespective of my
> comments, I think that cleanup could also be done as a follow-up patch after
> 3.11.

I'll address your comments and sent a v4. Hopefully it will be the last one.

Given the dependencies between the PWM TPU driver and board code, should I ask 
Simon to take the series in the SH Mobile tree (after receiving your ack of 
course) ?

> Thierry
> 
> P.S.: please not that I've switched email addresses and there's also a
> linux-pwm mailing list that you should Cc on PWM subsystem related
> patches. The info should have propagated to linux-next's MAINTAINERS.

OK, I'll make sure to CC the right addresses.

-- 
Regards,

Laurent Pinchart

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

WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH v3 0/5] Renesas TPU PWM support
Date: Thu, 13 Jun 2013 17:38:51 +0200	[thread overview]
Message-ID: <4097084.Y91d0ZYkWB@avalon> (raw)
In-Reply-To: <20130612101250.GB30841@mithrandir>

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

Hi Thierry,

On Wednesday 12 June 2013 12:12:51 Thierry Reding wrote:
> On Tue, Jun 11, 2013 at 03:45:39PM +0200, Laurent Pinchart wrote:
> [...]
> 
> > I believe I've addressed most comments received in response to v2, with
> > the exception of channel allocation at .request() time for which I haven't
> > received any answer to my questions. That will hopefully not be a
> > showstopper.
>
> I totally forgot to reply to that mail. Done now. Irrespective of my
> comments, I think that cleanup could also be done as a follow-up patch after
> 3.11.

I'll address your comments and sent a v4. Hopefully it will be the last one.

Given the dependencies between the PWM TPU driver and board code, should I ask 
Simon to take the series in the SH Mobile tree (after receiving your ack of 
course) ?

> Thierry
> 
> P.S.: please not that I've switched email addresses and there's also a
> linux-pwm mailing list that you should Cc on PWM subsystem related
> patches. The info should have propagated to linux-next's MAINTAINERS.

OK, I'll make sure to CC the right addresses.

-- 
Regards,

Laurent Pinchart

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

  reply	other threads:[~2013-06-13 15:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 13:45 [PATCH v3 0/5] Renesas TPU PWM support Laurent Pinchart
2013-06-11 13:45 ` Laurent Pinchart
2013-06-11 13:45 ` [PATCH v3 1/5] pwm: Add Renesas TPU PWM driver Laurent Pinchart
2013-06-11 13:45   ` Laurent Pinchart
2013-06-12 10:22   ` Thierry Reding
2013-06-12 10:22     ` Thierry Reding
2013-06-13 15:39     ` Laurent Pinchart
2013-06-13 15:39       ` Laurent Pinchart
2013-06-11 13:45 ` [PATCH v3 2/5] ARM: mach-shmobile: armadillo800eva: Add backlight support Laurent Pinchart
2013-06-11 13:45   ` Laurent Pinchart
2013-06-11 13:45 ` [PATCH v3 3/5] ARM: mach-shmobile: kota2: Use leds-pwm + pwm-rmob Laurent Pinchart
2013-06-11 13:45   ` Laurent Pinchart
2013-06-12  5:33   ` Magnus Damm
2013-06-12  5:33     ` Magnus Damm
2013-06-12  5:47     ` Simon Horman
2013-06-12  5:47       ` Simon Horman
2013-06-11 13:45 ` [PATCH v3 4/5] ARM: shmobile: sh73a0: Remove all GPIOs Laurent Pinchart
2013-06-11 13:45   ` Laurent Pinchart
2013-06-11 13:45 ` [PATCH v3 5/5] leds: Remove leds-renesas-tpu driver Laurent Pinchart
2013-06-11 13:45   ` Laurent Pinchart
2013-06-12 10:12 ` [PATCH v3 0/5] Renesas TPU PWM support Thierry Reding
2013-06-12 10:12   ` Thierry Reding
2013-06-13 15:38   ` Laurent Pinchart [this message]
2013-06-13 15:38     ` Laurent Pinchart

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=4097084.Y91d0ZYkWB@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.