linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
Cc: "linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"swarren@nvidia.com" <swarren@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] FTM PWM adds regmap and endianness support.
Date: Mon, 28 Apr 2014 16:56:16 +0200	[thread overview]
Message-ID: <20140428145615.GA28443@ulmo> (raw)
In-Reply-To: <e5e350afaa7b42cfbd93f52130560064@BY2PR03MB505.namprd03.prod.outlook.com>

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

On Mon, Apr 28, 2014 at 02:26:57PM +0000, Li.Xiubo@freescale.com wrote:
> 
> 
> 
> > > Xiubo Li (3):
> > >   pwm: ftm-pwm: Clean up the code.
> > >   pwm: ftm-pwm: Convert to direct regmap API usage.
> > >   pwm: ftm-pwm: Add big-endian support
> > >
> > >  drivers/pwm/pwm-fsl-ftm.c | 96 ++++++++++++++++++++++++++---------------------
> > >  1 file changed, 53 insertions(+), 43 deletions(-)
> >
> > This leaves me with only very vague idea of why this is necessary and
> > why it should be merged.
> >
> > Please describe in more detail (in both the cover-letter and each
> > individual patch) why you want me to apply these patches.
> >
> 
> Thanks very much for your reply.
> 
> Should I resend this patch series? If so, I will add some thing like the following:
> 
> The FTM PWM driver will be used in our Vybrid, LS1 and LS2+ SoCs, and on Vybrid
> and LS2 SoCs, the FTM devices are in LE mode, while on LS1 SoCs it in BE mode.
> 
> So this patch series add endianness support based on the regmap core, which has
> already support the rich endiannesses for the same device.

Yes, please resend with that description added where appropriate. I'd
like to see something like that in the cover letter and, more
importantly, in the individual patches.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-04-28 14:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  4:53 [PATCH 0/3] FTM PWM adds regmap and endianness support Xiubo Li
2014-03-21  4:53 ` [PATCH 1/3] pwm: ftm-pwm: Clean up the code Xiubo Li
2014-04-28 14:57   ` Thierry Reding
2014-04-28 15:16     ` Li.Xiubo
2014-03-21  4:53 ` [PATCH 2/3] pwm: ftm-pwm: Convert to direct regmap API usage Xiubo Li
2014-04-28 14:59   ` Thierry Reding
2014-04-28 15:14     ` Li.Xiubo
2014-03-21  4:53 ` [PATCH 3/3] pwm: ftm-pwm: Add big-endian support Xiubo Li
2014-04-28 15:02   ` Thierry Reding
2014-04-28 15:11     ` Li.Xiubo
2014-04-10  6:05 ` [PATCH 0/3] FTM PWM adds regmap and endianness support Li.Xiubo
2014-04-28 13:10 ` Thierry Reding
2014-04-28 14:26   ` Li.Xiubo
2014-04-28 14:56     ` Thierry Reding [this message]
2014-04-28 15:21       ` Li.Xiubo

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=20140428145615.GA28443@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=swarren@nvidia.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).