From: Jonathan Cameron <jic23@kernel.org>
To: Yannick Brosseau <yannick.brosseau@gmail.com>
Cc: lars@metafoo.de, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, fabrice.gasnier@foss.st.com,
olivier.moysan@foss.st.com, paul@crapouillou.net,
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 v2 0/2] iio: adc: stm32: Fix ADC IRQ handling on STM32F4
Date: Sun, 22 May 2022 12:44:57 +0100 [thread overview]
Message-ID: <20220522124457.3546c9c8@jic23-huawei> (raw)
In-Reply-To: <20220516203939.3498673-1-yannick.brosseau@gmail.com>
On Mon, 16 May 2022 16:39:37 -0400
Yannick Brosseau <yannick.brosseau@gmail.com> wrote:
> Changes to the STM32 ADC irq handling broke the STM32F4 platforms
> These two patches bring it back to a working state.
Applied to the fixes-togreg branch of iio.git and marked for stable.
Thanks,
Jonathan
>
> Changes:
> * Removed spurious IRQs detection
> * Updated comments and commit messages
>
> Yannick Brosseau (2):
> iio: adc: stm32: Fix ADCs iteration in irq handler
> iio: adc: stm32: Fix IRQs on STM32F4 by removing custom spurious IRQs
> message
>
> drivers/iio/adc/stm32-adc-core.c | 7 ++++++-
> drivers/iio/adc/stm32-adc.c | 10 ----------
> 2 files changed, 6 insertions(+), 11 deletions(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-22 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 20:39 [PATCH v2 0/2] iio: adc: stm32: Fix ADC IRQ handling on STM32F4 Yannick Brosseau
2022-05-16 20:39 ` [PATCH v2 1/2] iio: adc: stm32: Fix ADCs iteration in irq handler Yannick Brosseau
2022-05-17 8:56 ` Fabrice Gasnier
2022-05-16 20:39 ` [PATCH v2 2/2] iio: adc: stm32: Fix IRQs on STM32F4 by removing custom spurious IRQs message Yannick Brosseau
2022-05-17 8:56 ` Fabrice Gasnier
2022-05-22 11:44 ` 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=20220522124457.3546c9c8@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--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=paul@crapouillou.net \
--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