[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83D84516-8721-4712-B24B-7B1199FAFCC4@jic23.retrosnub.co.uk>
Date: Sat, 22 Sep 2018 13:51:22 +0100
From: Jonathan Cameron <jic23@...23.retrosnub.co.uk>
To: Himanshu Jha <himanshujha199640@...il.com>,
Jonathan Cameron <jic23@...nel.org>
CC: Eugen Hristev <eugen.hristev@...rochip.com>,
ludovic.desroches@...rochip.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org, nicolas.ferre@...rochip.com,
Maxime Ripard <maxime.ripard@...tlin.com>
Subject: Re: [PATCH 2/2] iio: adc: at91: fix wrong channel number in triggered buffer mode
On 22 September 2018 12:48:49 BST, Himanshu Jha <himanshujha199640@...il.com> wrote:
>On Sat, Sep 22, 2018 at 11:36:16AM +0100, Jonathan Cameron wrote:
>> On Fri, 21 Sep 2018 15:26:03 +0800
>> kbuild test robot <lkp@...el.com> wrote:
>>
>> > Hi Eugen,
>> This one is leaving me stumped...
>>
>> Anyone care to point out what I'm missing that is wrong here?
>>
>> Also Eugen, please don't cc stable on a patch directly. It is fine
>to send
>> a backport request once a patch has hit mainline, but before that
>it's just
>> adding noise to a list as they won't take it directly anyway.
>
>Song is correct on this one.
>
>So, just replace the declaration to:
>
> struct iio_chan_spec const *chan;
>
>and then warning goes away...
Good point. Not enough coffee this morning..
Obvious now :)
>
>Another thing, its better not to reply the automated bot and instead to
>the author by changing "From" address. :)
>
>That is what I do often when replying to that thread.
>
>https://lore.kernel.org/lkml/20180921182616.GA2077@himanshu-Vostro-3559/
>
>And it nests properly in the given thread avoiding any noise to kbuild
>bot.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists