From: Paul Cercueil <paul@crapouillou.net>
To: Yannick Brosseau <yannick.brosseau@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, fabrice.gasnier@foss.st.com,
olivier.moysan@foss.st.com, linux-iio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: adc: stm32: Fix ADC IRQ handling on STM32F4
Date: Sat, 07 May 2022 00:05:00 +0100 [thread overview]
Message-ID: <CGHHBR.49W7GPLHSYOE@crapouillou.net> (raw)
In-Reply-To: <20220506225617.1774604-1-yannick.brosseau@gmail.com>
Hi Yannick,
Le ven., mai 6 2022 at 18:56:15 -0400, Yannick Brosseau
<yannick.brosseau@gmail.com> a écrit :
> Recent changes to the STM32 ADC irq handling broke the STM32F4
> platforms
> These two patches bring it back to a working state.
If the STM32 ADC was broken recently, and these two patches fix it,
then I'd expect to see a Fixes: tag on both commits and Cc:
linux-stable.
Cheers,
-Paul
> Yannick Brosseau (2):
> iio: adc: stm32: Iterate through all ADCs in irq handler
> iio: adc: stm32: Fix check for spurious IRQs on STM32F4
>
> drivers/iio/adc/stm32-adc-core.c | 7 ++++++-
> drivers/iio/adc/stm32-adc.c | 9 ++++++---
> 2 files changed, 12 insertions(+), 4 deletions(-)
>
> --
> 2.36.0
>
next prev parent reply other threads:[~2022-05-06 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 22:56 Yannick Brosseau
2022-05-06 22:56 ` [PATCH 1/2] iio: adc: stm32: Iterate through all ADCs in irq handler Yannick Brosseau
2022-05-13 13:05 ` Fabrice Gasnier
2022-05-06 22:56 ` [PATCH 2/2] iio: adc: stm32: Fix check for spurious IRQs on STM32F4 Yannick Brosseau
2022-05-07 14:19 ` Jonathan Cameron
2022-05-13 13:13 ` Fabrice Gasnier
2022-05-06 23:05 ` Paul Cercueil [this message]
2022-05-07 13:58 ` [PATCH 0/2] iio: adc: stm32: Fix ADC IRQ handling " Jonathan Cameron
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=CGHHBR.49W7GPLHSYOE@crapouillou.net \
--to=paul@crapouillou.net \
--cc=alexandre.torgue@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.com \
--cc=yannick.brosseau@gmail.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
all inboxes | Powered by JetHome®