From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update file patterns for WOLFSON MICROELECTRONICS PMIC DRIVERS
Date: Tue, 8 Dec 2009 19:10:18 +0000 [thread overview]
Message-ID: <20091208191018.GB2590@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1260298457.27677.63.camel@Joe-Laptop.home>
On Tue, Dec 08, 2009 at 10:54:17AM -0800, Joe Perches wrote:
> On Tue, 2009-12-08 at 18:51 +0000, Mark Brown wrote:
> > Why not Documentation/hwmon/wm831x?
> Beats me, it's your entry, add all the appropriate ones.
It wasn't clear why you were adding one and not the other.
> Maybe:
> F: Documentation/hwmon/wm8*
That is possibly too general - the names are already very close to the
Winbond ones as it is, wm83?? might be safer.
prev parent reply other threads:[~2009-12-08 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 18:48 [PATCH] MAINTAINERS: Update file patterns for WOLFSON MICROELECTRONICS PMIC DRIVERS Joe Perches
2009-12-08 18:51 ` Mark Brown
2009-12-08 18:54 ` Joe Perches
2009-12-08 19: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=20091208191018.GB2590@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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