From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Peter Rosin <peda@axentia.se>,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [RESEND PATCH] mux: constify mux class
Date: Thu, 5 Dec 2024 10:12:13 +0100 [thread overview]
Message-ID: <2024120557-halt-enable-224d@gregkh> (raw)
In-Reply-To: <20241205085605.9501-1-brgl@bgdev.pl>
On Thu, Dec 05, 2024 at 09:56:05AM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> All class functions used here take a const pointer to the class
> structure so we can make the struct itself constant.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> Greg: Peter picked this up into his branch long before the v6.13 merge
> window, then never sent it upstream. Could you pick this up this time
> into your tree?
>
> drivers/mux/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mux/core.c b/drivers/mux/core.c
> index 78c0022697ec7..02be4ba372571 100644
> --- a/drivers/mux/core.c
> +++ b/drivers/mux/core.c
> @@ -42,7 +42,7 @@ struct mux_state {
> unsigned int state;
> };
>
> -static struct class mux_class = {
> +static const struct class mux_class = {
> .name = "mux",
> };
>
> --
> 2.45.2
>
Sure, will do, thanks. I should sweep the tree for the remaining ones
as well...
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-05 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:56 [RESEND PATCH] mux: constify mux class Bartosz Golaszewski
2024-12-05 9:12 ` Greg Kroah-Hartman [this message]
2025-01-02 9:21 ` Bartosz Golaszewski
2025-01-10 9:08 ` Greg Kroah-Hartman
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=2024120557-halt-enable-224d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.