From: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
To: "Antonio Borneo" <antonio.borneo@foss.st.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Gatien Chevallier" <gatien.chevallier@foss.st.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lee Jones" <lee@kernel.org>,
linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
"Olivier Moysan" <olivier.moysan@foss.st.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Subject: Re: [PATCH 3/5] iio: trigger: stm32-timer: Fix build warnings about export.h
Date: Tue, 10 Jun 2025 15:05:36 +0200 [thread overview]
Message-ID: <f8b1adef-10f3-4cff-9e11-10c1a16f6ec5@foss.st.com> (raw)
In-Reply-To: <20250610124855.269158-4-antonio.borneo@foss.st.com>
On 6/10/25 14:48, Antonio Borneo wrote:
> After commit a934a57a42f6 ("scripts/misc-check: check missing #include
> <linux/export.h> when W=1") and commit 7d95680d64ac ("scripts/misc-check:
> check unnecessary #include <linux/export.h> when W=1") we get the build
> warning with W=1:
>
> drivers/iio/trigger/stm32-timer-trigger.c: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing
>
> Fix it.
>
> Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
Hi Antonio,
You can add my:
Acked-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Thanks,
Fabrice
> ---
> drivers/iio/trigger/stm32-timer-trigger.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/trigger/stm32-timer-trigger.c b/drivers/iio/trigger/stm32-timer-trigger.c
> index 925b864facca1..3b9a3a6cbb25c 100644
> --- a/drivers/iio/trigger/stm32-timer-trigger.c
> +++ b/drivers/iio/trigger/stm32-timer-trigger.c
> @@ -6,6 +6,7 @@
> *
> */
>
> +#include <linux/export.h>
> #include <linux/iio/iio.h>
> #include <linux/iio/sysfs.h>
> #include <linux/iio/timer/stm32-timer-trigger.h>
next prev parent reply other threads:[~2025-06-10 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 12:48 [PATCH 0/5] STM32: Fix build warnings about export.h Antonio Borneo
2025-06-10 12:48 ` [PATCH 1/5] bus: stm32_firewall: " Antonio Borneo
2025-06-10 13:30 ` Gatien CHEVALLIER
2025-06-10 12:48 ` [PATCH 2/5] iio: adc: stm32-dfsdm: " Antonio Borneo
2025-06-10 13:05 ` Fabrice Gasnier
2025-06-11 16:34 ` Jonathan Cameron
2025-06-10 12:48 ` [PATCH 3/5] iio: trigger: stm32-timer: " Antonio Borneo
2025-06-10 13:05 ` Fabrice Gasnier [this message]
2025-06-11 16:36 ` Jonathan Cameron
2025-06-10 12:48 ` [PATCH 4/5] iio: trigger: stm32-lptimer: " Antonio Borneo
2025-06-10 13:05 ` Fabrice Gasnier
2025-06-11 16:37 ` Jonathan Cameron
2025-06-10 12:48 ` [PATCH 5/5] mfd: stm32-timers: " Antonio Borneo
2025-06-10 13:06 ` Fabrice Gasnier
2025-06-19 11:26 ` (subset) " Lee Jones
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=f8b1adef-10f3-4cff-9e11-10c1a16f6ec5@foss.st.com \
--to=fabrice.gasnier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andy@kernel.org \
--cc=antonio.borneo@foss.st.com \
--cc=dlechner@baylibre.com \
--cc=gatien.chevallier@foss.st.com \
--cc=jic23@kernel.org \
--cc=lee@kernel.org \
--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=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.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;
as well as URLs for NNTP newsgroup(s).