From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Ethan Tidmore" <ethantidmore06@gmail.com>
Cc: <jic23@kernel.org>, <andy@kernel.org>, <dlechner@baylibre.com>,
<nuno.sa@analog.com>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/9] iio: light: gp2ap020a00f: simplify locking with guard()
Date: Thu, 19 Feb 2026 20:38:28 -0600 [thread overview]
Message-ID: <DGJFVHM5C384.3J15UGDT3VGCX@gmail.com> (raw)
In-Reply-To: <aZVlU9SL9e1x8Vwu@smile.fi.intel.com>
On Wed Feb 18, 2026 at 1:08 AM CST, Andy Shevchenko wrote:
> On Tue, Feb 17, 2026 at 10:37:20PM -0600, Ethan Tidmore wrote:
>> Use the guard() cleanup handler to manage the device lock.
>> This simplifies the code by removing the need for manual unlocking
>> and goto error handling paths.
>
...
>
> What I meant in the my cover letter is that you need to take some pieces from
> my patches and incorporate them here, so this becomes
>
> return 0;
>
Understood, so with the first patch how should I credit you? With the
patches I'm splitting up that you gave, I know to just put my SOB. Just
unsure about the first.
Thanks,
ET
next prev parent reply other threads:[~2026-02-20 2:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 4:37 [PATCH v4 0/9] iio: light: gp2ap020a00f: General cleanup and Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 1/9] iio: light: gp2ap020a00f: simplify locking with guard() Ethan Tidmore
2026-02-18 7:08 ` Andy Shevchenko
2026-02-20 2:38 ` Ethan Tidmore [this message]
2026-02-20 7:43 ` Andy Shevchenko
2026-02-18 4:37 ` [PATCH v4 2/9] iio: light: gp2ap020a00f: correct return type to int Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 3/9] iio: light: gp2ap020a00f: Use correct types for 16-bit LE data Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 4/9] iio: light: gp2ap020a00f: Replace custom implementation of min() Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 5/9] iio: light: gp2ap020a00f: Return directly from the switch cases Ethan Tidmore
2026-02-19 19:32 ` Ethan Tidmore
2026-02-19 20:00 ` Andy Shevchenko
2026-02-18 4:37 ` [PATCH v4 6/9] iio: light: gp2ap020a00f: Use temporary variable for struct device Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 7/9] iio: light: gp2ap020a00f: Explicitly use string literal for driver name Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 8/9] iio: light: gp2ap020a00f: Remove trailing comma in termination entry Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 9/9] iio: light: gp2ap020a00f: Join some lines of code to be a single line Ethan Tidmore
2026-02-18 7:10 ` [PATCH v4 0/9] iio: light: gp2ap020a00f: General cleanup and Andy Shevchenko
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=DGJFVHM5C384.3J15UGDT3VGCX@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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