From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
Cc: nuno.sa@analog.com, linux-iio@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
David Lechner <dlechner@baylibre.com>
Subject: Re: [PATCH v3 0/2] iio: adc: adi-axi-adc: make sure DRP is locked on enable
Date: Sun, 2 Jun 2024 10:13:16 +0100 [thread overview]
Message-ID: <20240602101316.70c62784@jic23-huawei> (raw)
In-Reply-To: <20240531-dev-axi-adc-drp-v3-0-e3fa79447c67@analog.com>
On Fri, 31 May 2024 11:41:53 +0200
Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> wrote:
> Hi Jonathan,
>
> Here it goes my v3. Just splits the fix (with a proper tag) in it's own patch.
Applied to the togreg branch of iio.git and pushed out as testing for
all the normal reasons.
Jonathan
>
> ---
> Changes in v3:
> - Patch 1
> * New patch.
> - Patch 2
> * No changes.
> - Link to v2: https://lore.kernel.org/r/20240522-dev-axi-adc-drp-v2-1-b63c9790a48a@analog.com
>
> ---
> Nuno Sa (2):
> iio: adc: adi-axi-adc: don't allow concurrent enable/disable calls
> iio: adc: adi-axi-adc: make sure DRP is locked on enable
>
> drivers/iio/adc/adi-axi-adc.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
> ---
> base-commit: 5e3c5871138da700796587aa5f096d39135f9d36
> change-id: 20240506-dev-axi-adc-drp-ae6bd9d32617
> --
>
> Thanks!
> - Nuno Sá
>
>
prev parent reply other threads:[~2024-06-02 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:41 [PATCH v3 0/2] iio: adc: adi-axi-adc: make sure DRP is locked on enable Nuno Sa via B4 Relay
2024-05-31 9:41 ` [PATCH v3 1/2] iio: adc: adi-axi-adc: don't allow concurrent enable/disable calls Nuno Sa via B4 Relay
2024-05-31 9:41 ` [PATCH v3 2/2] iio: adc: adi-axi-adc: make sure DRP is locked on enable Nuno Sa via B4 Relay
2024-06-02 9:13 ` 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=20240602101316.70c62784@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devnull+nuno.sa.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@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