From: Jonathan Cameron <jic23@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Vasileios Amoiridis <vassilisamir@gmail.com>,
linux-iio@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] iio: pressure: bmp280-core: Make read-only const array conversion_time_max static
Date: Mon, 22 Jul 2024 21:01:11 +0100 [thread overview]
Message-ID: <20240722210111.49e66c4e@jic23-huawei> (raw)
In-Reply-To: <20240722151738.572913-1-colin.i.king@gmail.com>
On Mon, 22 Jul 2024 16:17:38 +0100
Colin Ian King <colin.i.king@gmail.com> wrote:
> Don't populate the read-only array conversion_time_max on the stack at
> run time, instead make it static.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
I'm almost 100% the compiler can hoist this off the stack if it feels like
it but sure, it might not and adding the static keyword probably obliges
it to do so. Is that better or worse? Probably better.
Ah well, I don't feel strongly and it's probably a good thing.
Applied to the testing branch of iio.git for now. I'll rebase on rc1 once available.
Thanks,
Jonathan
> ---
> drivers/iio/pressure/bmp280-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/pressure/bmp280-core.c b/drivers/iio/pressure/bmp280-core.c
> index 49081b729618..9ead52954de3 100644
> --- a/drivers/iio/pressure/bmp280-core.c
> +++ b/drivers/iio/pressure/bmp280-core.c
> @@ -1865,7 +1865,7 @@ EXPORT_SYMBOL_NS(bmp580_chip_info, IIO_BMP280);
>
> static int bmp180_wait_for_eoc(struct bmp280_data *data, u8 ctrl_meas)
> {
> - const int conversion_time_max[] = { 4500, 7500, 13500, 25500 };
> + static const int conversion_time_max[] = { 4500, 7500, 13500, 25500 };
> unsigned int delay_us;
> unsigned int ctrl;
> int ret;
next prev parent reply other threads:[~2024-07-22 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 15:17 [PATCH][next] iio: pressure: bmp280-core: Make read-only const array conversion_time_max static Colin Ian King
2024-07-22 20:01 ` Jonathan Cameron [this message]
2024-07-23 17:04 ` Dan Carpenter
2024-07-23 17:40 ` Colin King (gmail)
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=20240722210111.49e66c4e@jic23-huawei \
--to=jic23@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vassilisamir@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