From: Greg KH <gregkh@linuxfoundation.org>
To: Meng Shao Liu <sau525@gmail.com>
Cc: linux-kernel@vger.kernel.org, visitorckw@gmail.com
Subject: Re: [PATCH 2/2] samples/kobject: make attribute_group const
Date: Wed, 16 Jul 2025 06:53:14 +0200 [thread overview]
Message-ID: <2025071603-vacant-cable-0696@gregkh> (raw)
In-Reply-To: <170a918a8e14b1e0c003b6e277cd5813631c2749.1752634732.git.sau525@gmail.com>
On Wed, Jul 16, 2025 at 11:07:34AM +0800, Meng Shao Liu wrote:
> The attr_group structures are allocated once and never modified at
> runtime. Also to match the const‑qualified parameter of
> sysfs_create_group().
>
> Signed-off-by: Meng Shao Liu <sau525@gmail.com>
> ---
> samples/kobject/kobject-example.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/samples/kobject/kobject-example.c b/samples/kobject/kobject-example.c
> index e6d7fc18e..36d87ca0b 100644
> --- a/samples/kobject/kobject-example.c
> +++ b/samples/kobject/kobject-example.c
> @@ -102,7 +102,7 @@ static struct attribute *attrs[] = {
> * created for the attributes with the directory being the name of the
> * attribute group.
> */
> -static struct attribute_group attr_group = {
> +static const struct attribute_group attr_group = {
> .attrs = attrs,
> };
>
> --
> 2.43.0
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2025-07-16 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 3:07 [PATCH 1/2] samples/kobject: fix path comment Meng Shao Liu
2025-07-16 3:07 ` [PATCH 2/2] samples/kobject: make attribute_group const Meng Shao Liu
2025-07-16 4:53 ` Greg KH [this message]
2025-07-16 4:53 ` [PATCH 1/2] samples/kobject: fix path comment Greg KH
-- strict thread matches above, loose matches on Subject: below --
2025-07-15 14:30 [PATCH 2/2] samples/kobject: make attribute_group const Meng-Shao.Liu
2025-07-15 14:54 ` Greg KH
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=2025071603-vacant-cable-0696@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sau525@gmail.com \
--cc=visitorckw@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 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.