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>,
David Dajun Chen <dchen@diasemi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Patch v3 2/7] Regulator: DA9055 Regulator driver
Date: Mon, 29 Oct 2012 14:52:15 +0000 [thread overview]
Message-ID: <20121029145215.GA4511@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1351512478.17695.14.camel@dhruva>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Mon, Oct 29, 2012 at 05:37:58PM +0530, Ashish Jangam wrote:
> On Sat, 2012-10-27 at 22:59 +0100, Mark Brown wrote:
> > Always submit patches with subject lines appropriate for the subsystem,
> > this helps get your patch noticed. People do things like search their
> > mailboxes for subsystem prefixes when looking for things they need to
> > review.
> In subject line apart from "regulator" I will introduce "next" too.
No, that's not going to help. You need to actually include "regulator"
in the subject line and not a variation like "Regulator" which you've
used this time. In general if your commit log looks different to all
the other commit logs for the subsystem there's probably an issue.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-29 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 10:09 [Patch v3 2/7] Regulator: DA9055 Regulator driver Ashish Jangam
2012-10-23 10:02 ` Ashish Jangam
2012-10-23 11:05 ` Mark Brown
2012-10-27 21:59 ` Mark Brown
2012-10-29 12:07 ` Ashish Jangam
2012-10-29 14:52 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-11 6:36 Ashish Jangam
2012-10-11 10:02 ` Ashish Jangam
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=20121029145215.GA4511@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 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.