From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Francesco Dolcini" <francesco@dolcini.it>,
"João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>,
"Leonard Göhrs" <l.goehrs@pengutronix.de>,
kernel@pengutronix.de, "Oleksij Rempel" <o.rempel@pengutronix.de>,
"Roan van Dijk" <roan@protonic.nl>,
"Tomasz Duszynski" <tomasz.duszynski@octakon.com>,
"Jacopo Mondi" <jacopo@jmondi.org>,
"Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
"Mudit Sharma" <muditsharma.info@gmail.com>,
"Javier Carrasco" <javier.carrasco.cruz@gmail.com>,
"Ondřej Jirman" <megi@xff.cz>,
"Andreas Klinger" <ak@it-klinger.de>,
"Petre Rodan" <petre.rodan@subdimension.ro>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 00/28] iio: zero init stack with { } instead of memset()
Date: Thu, 12 Jun 2025 11:45:57 +0100 [thread overview]
Message-ID: <20250612114557.00007628@huawei.com> (raw)
In-Reply-To: <aEqbQPvz0FsLXt0Z@duo.ucw.cz>
On Thu, 12 Jun 2025 11:17:52 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> > Jonathan mentioned recently that he would like to get away from using
> > memset() to zero-initialize stack memory in the IIO subsystem. And we
> > have it on good authority that initializing a struct or array with = { }
> > is the preferred way to do this in the kernel [1]. So here is a series
> > to take care of that.
>
> 1) Is it worth the churn?
>
> 2) Will this fail to initialize padding with some obscure compiler?
>
> 3) Why do you believe that {} is the preffered way? All we have is
> Kees' email that explains that = {} maybe works in configs he tested.
>
Pavel,
I think main thing that matters in Kees email is there is a self test
that should fire if a compiler ever does this wrong.
Using this syntax is definitely not a 'kernel wide' preference yet
but I do prefer to make some changes like this in IIO just because it
reduces the amount of code that smells different when reviewing.
Given how many drivers we now have, sadly people pick different ones
to cut and paste from so we get a lot of new drivers that look like
how we preferred to do things 10 years ago :(
However it is a fair bit of churn. hmm. Let's let this sit for
a little while and see if other view points come in.
Thanks
Jonathan
> BR,
> Pavel
>
> > [1]:
> > https://lore.kernel.org/linux-iio/202505090942.48EBF01B@keescook/
>
>
>
> > ---
> > David Lechner (28):
> > iio: accel: adxl372: use = { } instead of memset()
> > iio: accel: msa311: use = { } instead of memset()
> > iio: adc: dln2-adc: use = { } instead of memset()
> > iio: adc: mt6360-adc: use = { } instead of memset()
> > iio: adc: rockchip_saradc: use = { } instead of memset()
> > iio: adc: rtq6056: use = { } instead of memset()
> > iio: adc: stm32-adc: use = { } instead of memset()
> > iio: adc: ti-ads1015: use = { } instead of memset()
> > iio: adc: ti-ads1119: use = { } instead of memset()
> > iio: adc: ti-lmp92064: use = { } instead of memset()
> > iio: adc: ti-tsc2046: use = { } instead of memset()
> > iio: chemical: scd4x: use = { } instead of memset()
> > iio: chemical: scd30: use = { } instead of memset()
> > iio: chemical: sunrise_co2: use = { } instead of memset()
> > iio: dac: ad3552r: use = { } instead of memset()
> > iio: imu: inv_icm42600: use = { } instead of memset()
> > iio: imu: inv_mpu6050: use = { } instead of memset()
> > iio: light: bh1745: use = { } instead of memset()
> > iio: light: ltr501: use = { } instead of memset()
> > iio: light: opt4060: use = { } instead of memset()
> > iio: light: veml6030: use = { } instead of memset()
> > iio: magnetometer: af8133j: use = { } instead of memset()
> > iio: pressure: bmp280: use = { } instead of memset()
> > iio: pressure: mpl3115: use = { } instead of memset()
> > iio: pressure: mprls0025pa: use = { } instead of memset()
> > iio: pressure: zpa2326: use = { } instead of memset()
> > iio: proximity: irsd200: use = { } instead of memset()
> > iio: temperature: tmp006: use = { } instead of memset()
> >
> > drivers/iio/accel/adxl372.c | 3 +--
> > drivers/iio/accel/msa311.c | 4 +---
> > drivers/iio/adc/dln2-adc.c | 4 +---
> > drivers/iio/adc/mt6360-adc.c | 3 +--
> > drivers/iio/adc/rockchip_saradc.c | 4 +---
> > drivers/iio/adc/rtq6056.c | 4 +---
> > drivers/iio/adc/stm32-adc.c | 3 +--
> > drivers/iio/adc/ti-ads1015.c | 4 +---
> > drivers/iio/adc/ti-ads1119.c | 4 +---
> > drivers/iio/adc/ti-lmp92064.c | 4 +---
> > drivers/iio/adc/ti-tsc2046.c | 3 +--
> > drivers/iio/chemical/scd30_core.c | 3 +--
> > drivers/iio/chemical/scd4x.c | 3 +--
> > drivers/iio/chemical/sunrise_co2.c | 6 ++----
> > drivers/iio/dac/ad3552r.c | 3 +--
> > drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c | 5 ++---
> > drivers/iio/imu/inv_icm42600/inv_icm42600_gyro.c | 5 ++---
> > drivers/iio/imu/inv_mpu6050/inv_mpu_acpi.c | 4 +---
> > drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c | 6 ++----
> > drivers/iio/light/bh1745.c | 4 +---
> > drivers/iio/light/ltr501.c | 4 +---
> > drivers/iio/light/opt4060.c | 4 +---
> > drivers/iio/light/veml6030.c | 4 +---
> > drivers/iio/magnetometer/af8133j.c | 4 +---
> > drivers/iio/pressure/bmp280-core.c | 5 +----
> > drivers/iio/pressure/mpl3115.c | 3 +--
> > drivers/iio/pressure/mprls0025pa_i2c.c | 5 +----
> > drivers/iio/pressure/zpa2326.c | 4 +---
> > drivers/iio/proximity/irsd200.c | 3 +--
> > drivers/iio/temperature/tmp006.c | 4 +---
> > 30 files changed, 34 insertions(+), 85 deletions(-)
> > ---
> > base-commit: 4c6073fec2fee4827fa0dd8a4ab4e6f7bbc05ee6
> > change-id: 20250611-iio-zero-init-stack-with-instead-of-memset-0d12d41a7ecb
> >
> > Best regards,
>
next prev parent reply other threads:[~2025-06-12 10:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 22:38 David Lechner
2025-06-11 22:38 ` [PATCH 01/28] iio: accel: adxl372: use = " David Lechner
2025-06-11 22:38 ` [PATCH 02/28] iio: accel: msa311: " David Lechner
2025-06-11 22:38 ` [PATCH 03/28] iio: adc: dln2-adc: " David Lechner
2025-06-11 22:38 ` [PATCH 04/28] iio: adc: mt6360-adc: " David Lechner
2025-06-11 22:38 ` [PATCH 05/28] iio: adc: rockchip_saradc: " David Lechner
2025-06-11 22:38 ` [PATCH 06/28] iio: adc: rtq6056: " David Lechner
2025-06-11 22:38 ` [PATCH 07/28] iio: adc: stm32-adc: " David Lechner
2025-06-11 22:39 ` [PATCH 08/28] iio: adc: ti-ads1015: " David Lechner
2025-06-11 22:39 ` [PATCH 09/28] iio: adc: ti-ads1119: " David Lechner
2025-06-12 8:16 ` Francesco Dolcini
2025-06-11 22:39 ` [PATCH 10/28] iio: adc: ti-lmp92064: " David Lechner
2025-06-12 5:41 ` Leonard Göhrs
2025-06-11 22:39 ` [PATCH 11/28] iio: adc: ti-tsc2046: " David Lechner
2025-06-12 4:30 ` Oleksij Rempel
2025-06-11 22:39 ` [PATCH 12/28] iio: chemical: scd4x: " David Lechner
2025-06-11 22:39 ` [PATCH 13/28] iio: chemical: scd30: " David Lechner
2025-06-11 22:39 ` [PATCH 14/28] iio: chemical: sunrise_co2: " David Lechner
2025-06-11 22:39 ` [PATCH 15/28] iio: dac: ad3552r: " David Lechner
2025-06-11 22:39 ` [PATCH 16/28] iio: imu: inv_icm42600: " David Lechner
2025-06-14 12:21 ` Jonathan Cameron
2025-06-11 22:39 ` [PATCH 17/28] iio: imu: inv_mpu6050: " David Lechner
2025-06-11 22:39 ` [PATCH 18/28] iio: light: bh1745: " David Lechner
2025-06-11 22:39 ` [PATCH 19/28] iio: light: ltr501: " David Lechner
2025-06-11 22:39 ` [PATCH 20/28] iio: light: opt4060: " David Lechner
2025-06-11 22:39 ` [PATCH 21/28] iio: light: veml6030: " David Lechner
2025-06-12 3:28 ` Javier Carrasco
2025-06-11 22:39 ` [PATCH 22/28] iio: magnetometer: af8133j: " David Lechner
2025-06-11 22:39 ` [PATCH 23/28] iio: pressure: bmp280: " David Lechner
2025-06-11 22:39 ` [PATCH 24/28] iio: pressure: mpl3115: " David Lechner
2025-06-11 22:39 ` [PATCH 25/28] iio: pressure: mprls0025pa: " David Lechner
2025-06-14 12:23 ` Jonathan Cameron
2025-06-11 22:39 ` [PATCH 26/28] iio: pressure: zpa2326: " David Lechner
2025-06-11 22:39 ` [PATCH 27/28] iio: proximity: irsd200: " David Lechner
2025-06-11 22:39 ` [PATCH 28/28] iio: temperature: tmp006: " David Lechner
2025-06-12 6:09 ` [PATCH 00/28] iio: zero init stack with " Nuno Sá
2025-06-12 9:17 ` Pavel Machek
2025-06-12 10:45 ` Jonathan Cameron [this message]
2025-06-12 12:11 ` Nicolas Frattaroli
2025-06-12 12:28 ` Andy Shevchenko
2025-06-12 18:54 ` Pavel Machek
2025-06-12 19:10 ` Andy Shevchenko
2025-06-14 6:47 ` Pavel Machek
2025-06-14 12:18 ` Jonathan Cameron
2025-06-14 14:18 ` Jonathan Cameron
2025-06-12 12:51 ` Andy Shevchenko
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=20250612114557.00007628@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ak@it-klinger.de \
--cc=alexandre.torgue@foss.st.com \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dlechner@baylibre.com \
--cc=francesco@dolcini.it \
--cc=heiko@sntech.de \
--cc=jacopo@jmondi.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=jpaulo.silvagoncalves@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.goehrs@pengutronix.de \
--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-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=megi@xff.cz \
--cc=michael.hennerich@analog.com \
--cc=muditsharma.info@gmail.com \
--cc=nuno.sa@analog.com \
--cc=o.rempel@pengutronix.de \
--cc=pavel@ucw.cz \
--cc=petre.rodan@subdimension.ro \
--cc=roan@protonic.nl \
--cc=tomasz.duszynski@octakon.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®