From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <ashish.jangam@kpitcummins.com>
Cc: Liam Girdwood <lrg@ti.com>, Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
David Dajun Chen <dchen@diasemi.com>
Subject: Re: [Patch v1 2/7] DA9055 Regulator driver
Date: Mon, 24 Sep 2012 11:10:15 +0100 [thread overview]
Message-ID: <20120924101014.GB21375@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1348477585.1639.1.camel@dhruva>
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.
prev parent reply other threads:[~2012-09-24 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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=20120924101014.GB21375@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ashish.jangam@kpitcummins.com \
--cc=dchen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox