From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Peter Rosin <peda@axentia.se>, Pavel Machek <pavel@ucw.cz>
Cc: linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Tin Huynh <tnhuynh@apm.com>, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Revert "i2c: mux: pca954x: Add ACPI support for pca954x"
Date: Sun, 26 Mar 2017 15:47:18 +0300 [thread overview]
Message-ID: <1490532438.708.10.camel@linux.intel.com> (raw)
In-Reply-To: <077d184d-1af5-fcdb-59c9-ff3255906be0@axentia.se>
On Fri, 2017-03-24 at 11:21 +0100, Peter Rosin wrote:
> On 2017-03-23 13:16, Andy Shevchenko wrote:
> > On Thu, 2017-03-23 at 12:21 +0100, Peter Rosin wrote:
> > > So, I'm still seeking guidance on how to handle these two patches.
> >
> > I have no strong opinion, but IDs might collide in the future if
> > PCAxxxx
> > will be assigned to something else and the patch will go stable@
> > (yeah,
> > OTOH it's quite unlikely).
> >
> > So, we may postpone any stable@ back porting up to some real issue
> > appears. Regarding second one, it's not important at all (could be
> > even
> > dropped). Consider it as example how to use _DSD and PRP0001 in ACPI
> > case for DT-enabled drivers.
>
> Ok, I have added 1/2 to my i2c-mux for-current branch and will drop
> 2/2 unless someone pipes up.
Fair enough.
Thanks!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-03-26 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:13 [PATCH v1 1/2] Revert "i2c: mux: pca954x: Add ACPI support for pca954x" Andy Shevchenko
2017-03-21 19:13 ` [PATCH v1 2/2] i2c: mux: pca954x: Allow enumeration via ACPI Andy Shevchenko
2017-03-22 10:23 ` [PATCH v1 1/2] Revert "i2c: mux: pca954x: Add ACPI support for pca954x" Peter Rosin
2017-03-22 13:05 ` Andy Shevchenko
2017-03-23 7:45 ` Peter Rosin
2017-03-23 10:04 ` Pavel Machek
2017-03-23 11:21 ` Peter Rosin
2017-03-23 12:16 ` Andy Shevchenko
2017-03-24 10:21 ` Peter Rosin
2017-03-26 12:47 ` Andy Shevchenko [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=1490532438.708.10.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=peda@axentia.se \
--cc=rpurdie@rpsys.net \
--cc=tnhuynh@apm.com \
--cc=wsa@the-dreams.de \
/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).