From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Kyungmin Park <kmpark@infradead.org>,
linux-kernel@vger.kernel.org, arnd@arndb.de,
kgene.kim@samsung.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] Samsung: Move Samsung SoCs GPIO drivers to drivers/gpio
Date: Fri, 27 May 2011 06:01:39 +0100 [thread overview]
Message-ID: <20110527050138.GA23418@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110527032243.GJ5032@ponder.secretlab.ca>
On Thu, May 26, 2011 at 09:22:43PM -0600, Grant Likely wrote:
> True, this does come down to personal taste, but unless someone has a
> really strong objection to it then I'll keep asking for new drivers to
> use gpio- as a prefix.
Right, my thought was more that if that's going to be the way forward
it's probably worth renaming the existing drivers so people don't get
confused - people are likely to pick the visible convention as their
first thought so we should either standardise on the existing one or
change what's there. It's nicer if what you're supposed to do is what
everyone's actually doing :)
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Samsung: Move Samsung SoCs GPIO drivers to drivers/gpio
Date: Fri, 27 May 2011 06:01:39 +0100 [thread overview]
Message-ID: <20110527050138.GA23418@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110527032243.GJ5032@ponder.secretlab.ca>
On Thu, May 26, 2011 at 09:22:43PM -0600, Grant Likely wrote:
> True, this does come down to personal taste, but unless someone has a
> really strong objection to it then I'll keep asking for new drivers to
> use gpio- as a prefix.
Right, my thought was more that if that's going to be the way forward
it's probably worth renaming the existing drivers so people don't get
confused - people are likely to pick the visible convention as their
first thought so we should either standardise on the existing one or
change what's there. It's nicer if what you're supposed to do is what
everyone's actually doing :)
next prev parent reply other threads:[~2011-05-27 5:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 5:44 [PATCH 0/4] Samsung: Move Samsung SoCs GPIO drivers to drivers/gpio Kyungmin Park
2011-05-20 5:44 ` Kyungmin Park
2011-05-20 6:31 ` Grant Likely
2011-05-20 6:31 ` Grant Likely
2011-05-21 11:21 ` Mark Brown
2011-05-21 11:21 ` Mark Brown
2011-05-27 3:22 ` Grant Likely
2011-05-27 3:22 ` Grant Likely
2011-05-27 5:01 ` Mark Brown [this message]
2011-05-27 5:01 ` Mark Brown
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=20110527050138.GA23418@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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.