From: Ben Gardner <gardner.ben@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()
Date: Thu, 9 Feb 2017 14:31:11 -0600 [thread overview]
Message-ID: <CAE7DoPYcU4+9CDKSXkhM3h0GZSvJe7r+mE4NGy5faBhZ39GHpg@mail.gmail.com> (raw)
In-Reply-To: <20170209195859.GB1431@katana>
On Thu, Feb 9, 2017 at 1:58 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
>
>> Note: Matching the driver to the I2C device requires another patch.
>> http://www.spinics.net/lists/linux-acpi/msg71914.html
>
> Do I get it right? With the patch applied we won't have a regression but
> the new feature will only be available when the above series is
> upstream? So, it is a "weak" dependency?
That is correct.
This patch shouldn't cause any regressions, but isn't useful without
the other patch series.
The other patch series was picked up today by Rafael J. Wysocki.
http://marc.info/?l=linux-acpi&m=148664872023023&w=2
Ben
next prev parent reply other threads:[~2017-02-09 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 19:53 [PATCH] eeprom/at24: use device_property_*() functions instead of of_get_property() Ben Gardner
2017-02-09 0:07 ` Andy Shevchenko
2017-02-09 15:27 ` Ben Gardner
2017-02-09 15:33 ` [PATCH v2] " Ben Gardner
2017-02-09 16:20 ` Andy Shevchenko
2017-02-09 17:03 ` Ben Gardner
2017-02-09 17:09 ` [PATCH v3] " Ben Gardner
2017-02-09 17:18 ` Ben Gardner
2017-02-09 17:36 ` [PATCH v4] " Ben Gardner
2017-02-09 17:43 ` Andy Shevchenko
2017-02-09 19:58 ` Wolfram Sang
2017-02-09 20:31 ` Ben Gardner [this message]
2017-02-10 15:34 ` Wolfram Sang
2017-02-09 20:35 ` [PATCH v2] " kbuild test robot
2017-02-09 21:30 ` Andy Shevchenko
2017-02-09 23:52 ` kbuild test robot
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=CAE7DoPYcU4+9CDKSXkhM3h0GZSvJe7r+mE4NGy5faBhZ39GHpg@mail.gmail.com \
--to=gardner.ben@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).