From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9] Regulator: Add Anatop regulator driver
Date: Wed, 7 Mar 2012 16:28:22 +0000 [thread overview]
Message-ID: <20120307162821.GP3107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120307153622.GC17745@game.jcrosoft.org>
On Wed, Mar 07, 2012 at 04:36:22PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > This really doesn't seem at all sane for a device which is already
> > vendor specific, it's just noise in the bindings.
> No it's
...?
> Here is a good example as we have regulator generic binding & vendor
> specific bindig
It's not vendor specific, it's device specific and people are doing it
even for devices with no generic bindings at all which is particularly
silly.
Device specific prefixes probably make sense, but vendor specific ones
are just noise.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120307/19e1a699/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: "Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linaro-dev@lists.linaro.org, Samuel Ortiz <sameo@linux.intel.com>,
patches@linaro.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lrg@ti.com>, Nancy Chen <Nancy.Chen@freescale.com>
Subject: Re: [PATCH v9] Regulator: Add Anatop regulator driver
Date: Wed, 7 Mar 2012 16:28:22 +0000 [thread overview]
Message-ID: <20120307162821.GP3107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120307153622.GC17745@game.jcrosoft.org>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Wed, Mar 07, 2012 at 04:36:22PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > This really doesn't seem at all sane for a device which is already
> > vendor specific, it's just noise in the bindings.
> No it's
...?
> Here is a good example as we have regulator generic binding & vendor
> specific bindig
It's not vendor specific, it's device specific and people are doing it
even for devices with no generic bindings at all which is particularly
silly.
Device specific prefixes probably make sense, but vendor specific ones
are just noise.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-07 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 13:24 [PATCH v9] Regulator: Add Anatop regulator driver Ying-Chun Liu (PaulLiu)
2012-03-07 13:24 ` Ying-Chun Liu (PaulLiu)
2012-03-07 13:22 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 13:22 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 13:45 ` Mark Brown
2012-03-07 13:45 ` Mark Brown
2012-03-07 15:36 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 15:36 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 16:28 ` Mark Brown [this message]
2012-03-07 16:28 ` 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=20120307162821.GP3107@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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.