[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121029145215.GA4511@opensource.wolfsonmicro.com>
Date: Mon, 29 Oct 2012 14:52:15 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Ashish Jangam <ashish.jangam@...tcummins.com>
Cc: Liam Girdwood <lrg@...com>, Samuel Ortiz <sameo@...ux.intel.com>,
David Dajun Chen <dchen@...semi.com>,
linux-kernel@...r.kernel.org
Subject: Re: [Patch v3 2/7] Regulator: DA9055 Regulator driver
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.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists