public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thierry.reding@avionic-design.de (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pwm: lpc32xx - Add a driver for the motor PWM
Date: Thu, 8 Nov 2012 09:27:00 +0100	[thread overview]
Message-ID: <20121108082700.GA21332@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <509B6B87.8030102@antcom.de>

On Thu, Nov 08, 2012 at 09:21:27AM +0100, Roland Stigge wrote:
> On 07/11/12 21:30, Thierry Reding wrote:
> > On Wed, Nov 07, 2012 at 06:19:38PM +0100, Roland Stigge wrote:
> >> On 07/11/12 17:30, Alban Bedel wrote:
> >>> Signed-off-by: Alban Bedel <alban.bedel@avionic-design.de> --- 
> >>> .../devicetree/bindings/pwm/lpc32xx-motor-pwm.txt  |   24 ++ 
> >>> arch/arm/boot/dts/lpc32xx.dtsi                     |    7 +
> >> 
> >> Is all this supposed to go via mach-lpc32xx -> arm-soc.git? Then,
> >> I can take this into the lpc32xx tree. Otherwise, you can split
> >> off the .dtsi file and I include it via lpc32xx.
> > 
> > I'd prefer a split between the arch/arm changes and the rest. I'll
> > take the drivers/pwm and Documentation changes through the PWM
> > tree.
> 
> OK, I'll organize everything lpc32xx specific under arch/arm/

Alban, I haven't finished reviewing yet, but once I'm done, can you
resubmit a set of two patches split by arch/arm and the rest?

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121108/e75de120/attachment.sig>

      reply	other threads:[~2012-11-08  8:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 16:30 [PATCH] pwm: lpc32xx - Add a driver for the motor PWM Alban Bedel
2012-11-07 17:19 ` Roland Stigge
2012-11-07 20:30   ` Thierry Reding
2012-11-08  8:21     ` Roland Stigge
2012-11-08  8:27       ` Thierry Reding [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=20121108082700.GA21332@avionic-0098.mockup.avionic-design.de \
    --to=thierry.reding@avionic-design.de \
    --cc=linux-arm-kernel@lists.infradead.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