From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"zhengxing@rock-chips.com" <zhengxing@rock-chips.com>,
"yang.a.fang@intel.com" <yang.a.fang@intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
John Lin <john.lin@realtek.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"koro.chen@mediatek.com" <koro.chen@mediatek.com>,
Bard Liao <bardliao@realtek.com>, Flove <flove@realtek.com>
Subject: Re: [PATCH 3/3] ASoC: rt5645: add device tree support
Date: Fri, 08 May 2015 14:05:56 -0500 [thread overview]
Message-ID: <554D0914.2040404@linux.intel.com> (raw)
In-Reply-To: <20150508164633.GA2761@sirena.org.uk>
On 5/8/15 11:46 AM, Mark Brown wrote:
> On Fri, May 08, 2015 at 08:30:52AM -0500, Pierre-Louis Bossart wrote:
>
>> Agree, but there wasn't a clear message provided to the readers of this
>> mailing list. A 'should' is a recommendation that provides no real incentive
>> to move to the new gpiod framework. The message would be clearer if
>> maintainers stated that new contributions using of_get_named_gpio() will no
>> longer be merged in the mainline (maybe after a specific milestone). That
>> would set the direction for everyone.
>
> That's what's been happening...
We are in agreement. I wasn't trying to argue but make sure everyone
noticed this change. I saw a commit with of_get_named_gpio in sound/soc
as recent as December 30, 2014 and we talked to 3rd parties unaware of
this change. Now they are :-)
next prev parent reply other threads:[~2015-05-08 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 13:42 [PATCH 1/3] ASoC: rt5645: fix add missing widget Bard Liao
2015-05-05 13:42 ` [PATCH 2/3] ASoC: rt5645: remove unused field in pdata Bard Liao
2015-05-06 17:50 ` Mark Brown
2015-05-05 13:42 ` [PATCH 3/3] ASoC: rt5645: add device tree support Bard Liao
2015-05-05 14:45 ` Liam Girdwood
2015-05-06 6:42 ` Bard Liao
2015-05-07 5:34 ` Bard Liao
2015-05-07 11:26 ` Liam Girdwood
2015-05-07 17:07 ` Rafael J. Wysocki
[not found] ` <20150508081339.GP1541@lahna.fi.intel.com>
2015-05-08 10:25 ` Mark Brown
2015-05-07 12:51 ` Mark Brown
2015-05-07 18:28 ` Pierre-Louis Bossart
2015-05-07 18:36 ` Mark Brown
2015-05-08 13:30 ` Pierre-Louis Bossart
2015-05-08 16:46 ` Mark Brown
2015-05-08 19:05 ` Pierre-Louis Bossart [this message]
2015-05-06 17:48 ` [PATCH 1/3] ASoC: rt5645: fix add missing widget 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=554D0914.2040404@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=flove@realtek.com \
--cc=john.lin@realtek.com \
--cc=koro.chen@mediatek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=oder_chiou@realtek.com \
--cc=yang.a.fang@intel.com \
--cc=zhengxing@rock-chips.com \
/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;
as well as URLs for NNTP newsgroup(s).