[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150518162859.GB2761@sirena.org.uk>
Date: Mon, 18 May 2015 17:28:59 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: Johan Hovold <johan@...nel.org>,
Support Opensource <support.opensource@...semi.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Milo Kim <milo.kim@...com>,
patches@...nsource.wolfsonmicro.com,
Fabio Estevam <fabio.estevam@...escale.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH 1/2] mfd: da9052: fix broken regulator probe
On Mon, May 18, 2015 at 11:13:55AM +0100, Lee Jones wrote:
> In future, for yourself and anyone else who is following this thread
> for 'fun', if a patch crosses multiple subsystems (which I try to keep
> to a minimum) it's probably best to indicate that in the subject line.
> mfd: regulator: <blah>
> ... would definitely get Marks attention. And yes, I know 'regulator'
> is mentioned in the subject line of the particular patch. :)
Yeah, sadly it's not visible in the thread view in mutt here since it's
too late in the subject line. That is good advice, though - the
standard thing is either like you describe or "mfd/regulator: ".
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists