From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>,
David Lechner <dlechner@baylibre.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iio: adc: ad7173: codestyle cleanup
Date: Sun, 19 Apr 2026 15:45:46 +0530 [thread overview]
Message-ID: <22A130DC-4980-453B-88DC-69998E79D511@gmail.com> (raw)
In-Reply-To: <ad3zB7nqgJ2BDS9w@ashevche-desk.local>
On 14 April 2026 1:25:51 pm IST, Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>On Mon, Apr 13, 2026 at 09:09:15AM -0500, David Lechner wrote:
>> On 4/13/26 8:42 AM, Sanjay Chitroda wrote:
>
>> > This patch series clean up error, warning(s) and a check reported
>> > with checkpatch and no functional behavior changes are intended.
>>
>> I'm pretty sure someone sent a series just like this already.
>>
>> Patches 2 and 3 were rejected. Patch 1 is probably OK.
>
>Seconded. NAK for patches 2 & 3 from me here.
>Patch 1 is OK, though.
>
Thank you David and Andy for the input.
Yes, similar changes is already available in iio/testing.
I have dropped this series.
prev parent reply other threads:[~2026-04-19 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 13:42 [PATCH 0/3] iio: adc: ad7173: codestyle cleanup Sanjay Chitroda
2026-04-13 13:42 ` [PATCH 1/3] iio: adc: ad7173: cleanup codestyle error Sanjay Chitroda
2026-04-13 13:42 ` [PATCH 2/3] iio: adc: ad7173: cleanup codestyle warning(s) Sanjay Chitroda
2026-04-13 13:42 ` [PATCH 3/3] iio: adc: ad7173: cleanup codestyle check and spell correct Sanjay Chitroda
2026-04-14 7:57 ` Andy Shevchenko
2026-04-14 16:51 ` Sanjay Chitroda
2026-04-13 14:09 ` [PATCH 0/3] iio: adc: ad7173: codestyle cleanup David Lechner
2026-04-14 7:55 ` Andy Shevchenko
2026-04-19 10:15 ` Sanjay Chitroda [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=22A130DC-4980-453B-88DC-69998E79D511@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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