From: Mark Brown <broonie@kernel.org>
To: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
Cc: Dirk Behme <dirk.behme@de.bosch.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Gokulkrishnan Nagarajan <Gokulkrishnan.Nagarajan@in.bosch.com>,
Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] regulator: core: GPIO #0 is a valid GPIO
Date: Wed, 3 Sep 2014 12:01:16 +0100 [thread overview]
Message-ID: <20140903110116.GI29327@sirena.org.uk> (raw)
In-Reply-To: <5406D98D.7000402@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Wed, Sep 03, 2014 at 01:04:13PM +0400, Dmitry Eremin-Solenikov wrote:
> OK, if the question is about other users, should we review all current users
> that do not specify that gpio, change them to pass -1 and then allow valid
> GPIO#0 as a valid ena_gpio? What do you think about a patch
> that will warn for one or two releases that ena_gpio == 0 will change
> meaning in a forthcoming feature?
The warning is sensible (I'm sure we used to have one though I can't see
it in the git logs now) but I'm not sure a two release cycle is enough
for everyone to have upgraded and paid attention.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-03 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:19 Dmitry Eremin-Solenikov
2014-08-29 19:01 ` Mark Brown
2014-09-01 7:46 ` Dirk Behme
2014-09-01 7:55 ` Geert Uytterhoeven
2014-09-01 10:15 ` Mark Brown
2014-09-01 11:59 ` Dmitry Eremin-Solenikov
2014-09-01 12:06 ` Mark Brown
2014-09-01 12:35 ` Dmitry Eremin-Solenikov
2014-09-01 12:49 ` Mark Brown
2014-09-03 9:04 ` Dmitry Eremin-Solenikov
2014-09-03 11:01 ` Mark Brown [this message]
2014-09-04 17:15 ` Linus Walleij
2014-09-04 17:19 ` Linus Walleij
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=20140903110116.GI29327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Gokulkrishnan.Nagarajan@in.bosch.com \
--cc=dirk.behme@de.bosch.com \
--cc=dmitry_eremin@mentor.com \
--cc=grant.likely@secretlab.ca \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome