From: Marek Vasut <marek.vasut@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Marek Vasut <marek.vasut+renesas@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: adc: handle unknow of_device_id data
Date: Wed, 8 Feb 2017 02:13:54 +0100 [thread overview]
Message-ID: <6f13a6fe-028e-e9af-db16-4d77e6c40d82@gmail.com> (raw)
In-Reply-To: <1ab64563-e536-ab8a-5d1e-f77cbf519dda@kernel.org>
On 02/05/2017 10:32 AM, Jonathan Cameron wrote:
> On 04/02/17 21:47, Marek Vasut wrote:
>> On 02/04/2017 10:44 PM, Arnd Bergmann wrote:
>>> On Sat, Feb 4, 2017 at 10:11 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>> On 02/03/2017 06:01 PM, Arnd Bergmann wrote:
>>>>> diff --git a/drivers/iio/adc/rcar-gyroadc.c b/drivers/iio/adc/rcar-gyroadc.c
>>>>> index 0c44f72c32a8..331ff9a673be 100644
>>>>> --- a/drivers/iio/adc/rcar-gyroadc.c
>>>>> +++ b/drivers/iio/adc/rcar-gyroadc.c
>>>>> @@ -336,7 +336,7 @@ static int rcar_gyroadc_parse_subdevs(struct iio_dev *indio_dev)
>>>>> struct device_node *child;
>>>>> struct regulator *vref;
>>>>> unsigned int reg;
>>>>> - unsigned int adcmode, childmode;
>>>>> + unsigned int adcmode = -1, childmode;
>>>>> unsigned int sample_width;
>>>>> unsigned int num_channels;
>>>>> int ret, first = 1;
>>>>> @@ -366,6 +366,9 @@ static int rcar_gyroadc_parse_subdevs(struct iio_dev *indio_dev)
>>>>> channels = rcar_gyroadc_iio_channels_3;
>>>>> num_channels = ARRAY_SIZE(rcar_gyroadc_iio_channels_3);
>>>>> break;
>>>>> + default:
>>>>> + dev_err(dev, "unknown device type");
>>>>
>>>> Is this verbose output really needed ?
>>>
>>> I don't care much either way, I was just trying to follow what the function does
>>> for the other failure cases. We can probably drop it though, as this
>>> would indicate
>>> a bug in the driver implementation, while the others are about
>>> incorrect DT data.
>>
>> I don't really want to pester you too much with minor details, let's
>> wait for JIC's opinion. If you're resending, please add my Ack,
>> otherwise consider this patch:
>>
>> Acked-by: Marek Vasut <marek.vasut@gmail.com>
>>
> I've applied with the dev_err dropped. Didn't care that much either
> way :)
Noone seems to care much, but everyone is slightly opinionated, hehe :)
> Anyhow, applied to the fixes-togreg-post-rc1 branch of iio.git as
> I might not get another pull request out pre the merge window.
> (if I do I'll apply it with that).
>
> Thanks,
>
> Jonathan
>
Thanks
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2017-02-08 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 17:01 [PATCH] iio: adc: handle unknow of_device_id data Arnd Bergmann
2017-02-04 21:11 ` Marek Vasut
2017-02-04 21:44 ` Arnd Bergmann
2017-02-04 21:47 ` Marek Vasut
2017-02-05 9:32 ` Jonathan Cameron
2017-02-08 1:13 ` Marek Vasut [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=6f13a6fe-028e-e9af-db16-4d77e6c40d82@gmail.com \
--to=marek.vasut@gmail.com \
--cc=arnd@arndb.de \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=pmeerw@pmeerw.net \
/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).