From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: potentiometer: tpl0102: change i2c functionality return code
Date: Sat, 5 Mar 2016 14:01:32 +0000 [thread overview]
Message-ID: <56DAE6BC.9060809@kernel.org> (raw)
In-Reply-To: <CAKzfze9u7bOZKD9+nU5qJGN4SDaaLu+jWXPRKHx=1x7e0=BfyQ@mail.gmail.com>
On 05/03/16 07:05, Matt Ranostay wrote:
> Bit embarrassing that I missed my new driver in the original cleanup :)
>
> On Fri, Mar 4, 2016 at 10:55 PM, Matt Ranostay <mranostay@gmail.com> wrote:
>> Change i2c_check_functionality condition check return from ENOTSUPP to
>> EOPNOTSUPP which is now the standard return code.
>>
>> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
Applied to the togreg branch of iio.git - probably will have to wait for the next cycle
now unless there is a big delay in the merge window for some reason.
Jonathan
>> ---
>> drivers/iio/potentiometer/tpl0102.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/iio/potentiometer/tpl0102.c b/drivers/iio/potentiometer/tpl0102.c
>> index 313124b..5c304d4 100644
>> --- a/drivers/iio/potentiometer/tpl0102.c
>> +++ b/drivers/iio/potentiometer/tpl0102.c
>> @@ -118,7 +118,7 @@ static int tpl0102_probe(struct i2c_client *client,
>>
>> if (!i2c_check_functionality(client->adapter,
>> I2C_FUNC_SMBUS_WORD_DATA))
>> - return -ENOTSUPP;
>> + return -EOPNOTSUPP;
>>
>> indio_dev = devm_iio_device_alloc(dev, sizeof(*data));
>> if (!indio_dev)
>> --
>> 2.7.0
>>
> --
> 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-03-05 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 6:55 [PATCH] iio: potentiometer: tpl0102: change i2c functionality return code Matt Ranostay
2016-03-05 7:05 ` Matt Ranostay
2016-03-05 14:01 ` 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=56DAE6BC.9060809@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@gmail.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).