From: Jonathan Cameron <jic23@kernel.org>
To: Trevor Gamblin <tgamblin@baylibre.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Alexandru Ardelean" <aardelean@baylibre.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw()
Date: Sun, 1 Dec 2024 13:23:43 +0000 [thread overview]
Message-ID: <20241201132343.3878d7a5@jic23-huawei> (raw)
In-Reply-To: <f4cb05ec-6b94-4c63-bf42-2fbd40dfd532@baylibre.com>
On Tue, 19 Nov 2024 14:09:45 -0500
Trevor Gamblin <tgamblin@baylibre.com> wrote:
> On 2024-11-19 13:36, Uwe Kleine-König wrote:
> > When struct ad_sigma_delta::keep_cs_asserted was introduced only
> > register writing was adapted to honor this new flag. Also respect it
> > when reading a register.
> >
> > Fixes: df1d80aee963 ("iio: ad_sigma_delta: Properly handle SPI bus locking vs CS assertion")
> > Signed-off-by: Uwe Kleine-König<u.kleine-koenig@baylibre.com>
> Reviewed-by: Trevor Gamblin <tgamblin@baylibre.com>
Hi Uwe,
Thanks for all these cleanups. Trivial request for future though.
If like this time the maintainer is being slow / busy and take a while
to come back so you roll up multiple fixes into a new series that's fine.
However, please just drop a quick reply on the original threads to make
it easier to notice that! Only needed if all the feedback like here has
been positive and the patch might get picked up directly from the wrong
version.
Thanks,
Jonathan
prev parent reply other threads:[~2024-12-01 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 18:36 [PATCH] iio: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() Uwe Kleine-König
[not found] ` <f4cb05ec-6b94-4c63-bf42-2fbd40dfd532@baylibre.com>
2024-12-01 13:23 ` 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=20241201132343.3878d7a5@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=aardelean@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=tgamblin@baylibre.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