From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: imu: bno055: make bno055_sysfs_attr const
Date: Sun, 29 Jun 2025 18:14:41 +0100 [thread overview]
Message-ID: <20250629181441.3173ee5d@jic23-huawei> (raw)
In-Reply-To: <20250628-iio-const-data-19-v1-1-a17e7c16b122@baylibre.com>
On Sat, 28 Jun 2025 12:35:36 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Add const qualifier to struct bno055_sysfs_attr and its array fields.
> All of this is read-only data so it can be made const.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
I was a little more dubious about this one and whether the scope of the changes
made it not worthwhile. Still const when possible is always good so
applied to the testing branch.
Thanks,
Jonathan
prev parent reply other threads:[~2025-06-29 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 17:35 [PATCH] iio: imu: bno055: make bno055_sysfs_attr const David Lechner
2025-06-29 17:14 ` 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=20250629181441.3173ee5d@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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