From: Ashish Jangam <ashish.jangam@kpitcummins.com>
To: broonie@opensource.wolfsonmicro.com
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-input@vger.kernel.org, David Dajun Chen <dchen@diasemi.com>
Subject: Re: [Patch v1 2/7] DA9055 Regulator driver
Date: Tue, 25 Sep 2012 14:15:53 +0530 [thread overview]
Message-ID: <1348562753.6795.19.camel@dhruva> (raw)
In-Reply-To: <C3AE124F08223B42BC95AEB82F0F6CED3353338A@KCHJEXMB03.kpit.com>
On Mon, 2012-09-24 at 18:04 +0530, Ashish Jangam wrote:
>
> -----Original Message-----
> From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> Sent: Monday, September 24, 2012 3:40 PM
> To: Ashish Jangam
> Cc: Liam Girdwood; Samuel Ortiz; linux-kernel@vger.kernel.org; David Dajun Chen
> Subject: Re: [Patch v1 2/7] DA9055 Regulator driver
>
> On Mon, Sep 24, 2012 at 02:36:25PM +0530, Ashish Jangam wrote:
> > Any update on this patch?
>
> Don't top post or send contentless pings.
>
> The general quality problems with your submissions don't encourage fast
> review both technically and in terms of reviewer enthusiasm; for example
> in this case the fact that you've not used a subject line appropriate
> for the subsystem means that your patch doesn't flag as such.
>
The motive behind the ping was to close on MFD earlier as other patches depends upon it.
Regulator framework takes care of most of the stuff therefore this patch is somewhat
simplified except the GPIO part which I will try to simplify it further and will post all the
non-ACK patches again with the correct subject line.
next parent reply other threads:[~2012-09-25 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3AE124F08223B42BC95AEB82F0F6CED3353338A@KCHJEXMB03.kpit.com>
2012-09-25 8:45 ` Ashish Jangam [this message]
2012-09-14 13:26 [Patch v1 2/7] DA9055 Regulator driver Ashish Jangam
2012-09-24 9:06 ` Ashish Jangam
2012-09-24 10:10 ` Mark Brown
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=1348562753.6795.19.camel@dhruva \
--to=ashish.jangam@kpitcummins.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dchen@diasemi.com \
--cc=linux-input@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.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.