[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2936f505-79d9-340e-4454-ec7ef0bc7236@axentia.se>
Date: Wed, 1 Feb 2017 11:18:20 +0100
From: Peter Rosin <peda@...ntia.se>
To: Peter Meerwald-Stadler <pmeerw@...erw.net>
CC: <linux-kernel@...r.kernel.org>,
Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Alison Schofield <amsfield22@...il.com>,
Gregor Boirie <gregor.boirie@...rot.com>,
Sanchayan Maity <maitysanchayan@...il.com>,
Ken Lin <ken.lin@...antech.com>, <linux-iio@...r.kernel.org>
Subject: Re: [PATCH 1/2] iio: pressure: mpl3115: do not rely on structure
field ordering
On 2017-02-01 10:57, Peter Meerwald-Stadler wrote:
>>> - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
>>> BIT(IIO_CHAN_INFO_SCALE),
>>> + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |
>>> BIT(IIO_CHAN_INFO_SCALE),
>>> as originally intended
>>
>> I considered that option, but the code in mpl3115_read_raw (and
>> mpl115_read_raw for that matter) return constants fro these values which
>> to me indicated that they were not "separate" and as that would also be
>> the change which replicated the exact behavior from before the regression
>> I went with that. But I don't care either way, so I can re-spin if you
>> want me to? (But don't blame me if that regresses in some other
>> interesting way).
>
> no, all good; shared_by_type is the way to go
> I'd rather respin for the not ORed comment in the patch
Ok, but I think I'll wait a bit so that Ken Lin gets some time to verify
that it actually solves the original problem. It should, but...
Cheers,
peda
Powered by blists - more mailing lists