From: Jonathan Cameron <jic23@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "Pengpeng Hou" <pengpeng@iscas.ac.cn>,
linux-iio@vger.kernel.org, "Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Matti Vaittinen" <mazziesaccount@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: light: rpr0521: Propagate regcache_sync() errors
Date: Sat, 11 Jul 2026 23:40:03 +0100 [thread overview]
Message-ID: <20260711234003.045e8685@jic23-huawei> (raw)
In-Reply-To: <8774ce7a-47a0-459b-b09a-7faef0d0fef3@web.de>
On Sat, 4 Jul 2026 09:54:11 +0200
Markus Elfring <Markus.Elfring@web.de> wrote:
> …
> > Return the regcache_sync() error so resume does not hide a failed
> > register restore.
>
> How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
A valid question to ask. In this particular case I'm going to treat it is
hardening against a failure that hasn't been observed in practice and
apply it. Note I also added the blank line that Andy called out in a similar
patch.
Applied to the testing branch of iio.git.
Thanks,
Jonathan
>
> See also:
> * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.2-rc1#n145
> * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.2-rc1#n34
>
>
> Regards,
> Markus
prev parent reply other threads:[~2026-07-11 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 7:15 Pengpeng Hou
2026-07-04 7:54 ` Markus Elfring
2026-07-11 22:40 ` Jonathan Cameron [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=20260711234003.045e8685@jic23-huawei \
--to=jic23@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=nuno.sa@analog.com \
--cc=pengpeng@iscas.ac.cn \
--cc=sakari.ailus@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=u.kleine-koenig@baylibre.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
Powered by JetHome