* [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED
@ 2026-08-31 10:09 Javier Carrasco
2026-08-31 11:47 ` Andy Shevchenko
0 siblings, 1 reply; 5+ messages in thread
From: Javier Carrasco @ 2026-08-31 10:09 UTC (permalink / raw)
To: Jonathan Cameron, David Lechner, Nuno Sá, Andy Shevchenko
Cc: linux-iio, linux-kernel, Javier Carrasco
Update the kernel-doc reference left over from an earlier revision
of the series, before the macro was renamed to IIO_DEV_ACQUIRE_FAILED().
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
Trivial documentation stuff that I found while getting the next version
of the veml6031x00 driver ready.
---
include/linux/iio/iio.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
index 711c00f67371..989c1db8fb36 100644
--- a/include/linux/iio/iio.h
+++ b/include/linux/iio/iio.h
@@ -789,7 +789,7 @@ DEFINE_GUARD_COND(__priv__iio_dev_mode_lock, _try_direct,
*
* Tries to acquire the direct mode lock with cleanup ACQUIRE() semantics and
* automatically releases it at the end of the scope. It most be always paired
- * with IIO_DEV_ACQUIRE_ERR(), for example (notice the scope braces)::
+ * with IIO_DEV_ACQUIRE_FAILED(), for example (notice the scope braces)::
*
* switch() {
* case IIO_CHAN_INFO_RAW: {
---
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
change-id: 20260831-doc_acquire_failed-bd0f94415e2f
Best regards,
--
Javier Carrasco <javier.carrasco.cruz@gmail.com>
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED
2026-08-31 10:09 [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED Javier Carrasco
@ 2026-08-31 11:47 ` Andy Shevchenko
2026-08-31 12:30 ` Joshua Crofts
0 siblings, 1 reply; 5+ messages in thread
From: Andy Shevchenko @ 2026-08-31 11:47 UTC (permalink / raw)
To: Javier Carrasco
Cc: Jonathan Cameron, David Lechner, Nuno Sá, Andy Shevchenko,
linux-iio, linux-kernel
On Mon, Aug 31, 2026 at 12:09:09PM +0200, Javier Carrasco wrote:
> Update the kernel-doc reference left over from an earlier revision
> of the series, before the macro was renamed to IIO_DEV_ACQUIRE_FAILED().
I would argue that it might be good to be backported, but who reads documentation?
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED
2026-08-31 11:47 ` Andy Shevchenko
@ 2026-08-31 12:30 ` Joshua Crofts
2026-08-31 13:07 ` Javier Carrasco
0 siblings, 1 reply; 5+ messages in thread
From: Joshua Crofts @ 2026-08-31 12:30 UTC (permalink / raw)
To: Andy Shevchenko
Cc: Javier Carrasco, Jonathan Cameron, David Lechner, Nuno Sá,
Andy Shevchenko, linux-iio, linux-kernel
On Mon, 31 Aug 2026 14:47:54 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Mon, Aug 31, 2026 at 12:09:09PM +0200, Javier Carrasco wrote:
> > Update the kernel-doc reference left over from an earlier revision
> > of the series, before the macro was renamed to IIO_DEV_ACQUIRE_FAILED().
>
> I would argue that it might be good to be backported, but who reads documentation?
Only LLMs these days...
--
Kind regards,
Joshua Crofts
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED
2026-08-31 12:30 ` Joshua Crofts
@ 2026-08-31 13:07 ` Javier Carrasco
2026-09-01 16:00 ` Jonathan Cameron
0 siblings, 1 reply; 5+ messages in thread
From: Javier Carrasco @ 2026-08-31 13:07 UTC (permalink / raw)
To: Joshua Crofts, Andy Shevchenko
Cc: Javier Carrasco, Jonathan Cameron, David Lechner, Nuno Sá,
Andy Shevchenko, linux-iio, linux-kernel
On Mon Aug 31, 2026 at 2:30 PM CEST, Joshua Crofts wrote:
> On Mon, 31 Aug 2026 14:47:54 +0300
> Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
>> On Mon, Aug 31, 2026 at 12:09:09PM +0200, Javier Carrasco wrote:
>> > Update the kernel-doc reference left over from an earlier revision
>> > of the series, before the macro was renamed to IIO_DEV_ACQUIRE_FAILED().
>>
>> I would argue that it might be good to be backported, but who reads documentation?
>
> Only LLMs these days...
And at least one human ;)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED
2026-08-31 13:07 ` Javier Carrasco
@ 2026-09-01 16:00 ` Jonathan Cameron
0 siblings, 0 replies; 5+ messages in thread
From: Jonathan Cameron @ 2026-09-01 16:00 UTC (permalink / raw)
To: Javier Carrasco
Cc: Joshua Crofts, Andy Shevchenko, David Lechner, Nuno Sá,
Andy Shevchenko, linux-iio, linux-kernel
On Mon, 31 Aug 2026 15:07:06 +0200
"Javier Carrasco" <javier.carrasco.cruz@gmail.com> wrote:
> On Mon Aug 31, 2026 at 2:30 PM CEST, Joshua Crofts wrote:
> > On Mon, 31 Aug 2026 14:47:54 +0300
> > Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> >
> >> On Mon, Aug 31, 2026 at 12:09:09PM +0200, Javier Carrasco wrote:
> >> > Update the kernel-doc reference left over from an earlier revision
> >> > of the series, before the macro was renamed to IIO_DEV_ACQUIRE_FAILED().
> >>
> >> I would argue that it might be good to be backported, but who reads documentation?
> >
> > Only LLMs these days...
>
> And at least one human ;)
Applied. Not backported as at least to humans it should be easy to figure out
what it should be once grep doesn't find any instances of _FAILED() form.
Thanks
Jonathan
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-09-01 16:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-31 10:09 [PATCH] iio: rename stale IIO_DEV_ACQUIRE_ERR reference to IIO_DEV_ACQUIRE_FAILED Javier Carrasco
2026-08-31 11:47 ` Andy Shevchenko
2026-08-31 12:30 ` Joshua Crofts
2026-08-31 13:07 ` Javier Carrasco
2026-09-01 16:00 ` Jonathan Cameron
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox