From: Jonathan Cameron <jic23@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Alison Schofield <amsfield22@gmail.com>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] staging: iio: light: isl29018/28: remove I2C_CLASS_HWMON .class setting
Date: Sun, 24 Jul 2016 12:30:08 +0100 [thread overview]
Message-ID: <6c46ec72-3cf2-0b8a-9a1f-38341573ccef@kernel.org> (raw)
In-Reply-To: <0d515ff9-252a-a8f9-49c1-89ef0b1e9887@kernel.org>
On 20/07/16 16:08, Jonathan Cameron wrote:
> On 19/07/16 08:13, Wolfram Sang wrote:
>> On Mon, Jul 18, 2016 at 02:30:46PM +0100, Jonathan Cameron wrote:
>>> On 18/07/16 09:50, Laxman Dewangan wrote:
>>>>
>>>> On Saturday 16 July 2016 07:58 AM, Alison Schofield wrote:
>>>>> I2C_CLASS_HWMON is for a hardware monitoring chip wanting
>>>>> auto-detection. IIO drivers don't typically use .class.
>>>>> Remove it.
>>>>>
>>>>> Signed-off-by: Alison Schofield <amsfield22@gmail.com>
>>>>> Cc: Daniel Baluta <daniel.baluta@gmail.com>
>>>>>
>>>>
>>>> Agree.
>>>> Acked-by: Laxman Dewangan <ldewangan@nvidia.com>
>>> Any resulting ABI change from dropping it?
>>
>> What do you mean with ABI? This is only relevant for "automatic"
>> instantiation.
> Cool, I was just being paranoid and didn't have time to check!
>
> Thanks,
>
> Jonathan
>> From me:
>>
>> Acked-by: Wolfram Sang <wsa@the-dreams.de>
>>
>
Applied to the togreg branch of iio.git - initially pushed out
as testing for the autoubuilders to play with it.
thanks,
Jonathan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-07-24 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 2:28 Alison Schofield
2016-07-18 8:50 ` Laxman Dewangan
2016-07-18 13:30 ` Jonathan Cameron
2016-07-19 7:13 ` Wolfram Sang
2016-07-20 15:08 ` Jonathan Cameron
2016-07-24 11:30 ` Jonathan Cameron [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=6c46ec72-3cf2-0b8a-9a1f-38341573ccef@kernel.org \
--to=jic23@kernel.org \
--cc=amsfield22@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--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
Powered by JetHome