From: Greg KH <gregkh@linuxfoundation.org>
To: Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com>
Cc: ayaanmirza85@gmail.com, dakr@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drivers/base: fix checkpatch.pl warnings in attribute_container.c (v2)
Date: Fri, 28 Feb 2025 23:31:46 -0800 [thread overview]
Message-ID: <2025022827-gesture-matted-d400@gregkh> (raw)
In-Reply-To: <20250227124417.132020-3-ayaanmirzabaig85@gmail.com>
On Thu, Feb 27, 2025 at 06:11:28PM +0530, Ayaan Mirza Baig wrote:
> This patch applies only cosmetic changes such as
> whitespace fixes, formatting and typos. These
> changes are flagged by checkpatch.pl
>
> Signed-off-by: Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com>
> ---
> drivers/base/attribute_container.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/attribute_container.c b/drivers/base/attribute_container.c
> index b6f941a6ab69..69637b2ec3bc 100644
> --- a/drivers/base/attribute_container.c
> +++ b/drivers/base/attribute_container.c
> @@ -5,7 +5,7 @@
> * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>
> *
> * The basic idea here is to enable a device to be attached to an
> - * aritrary numer of classes without having to allocate storage for them.
> + * aritrary number of classes without having to allocate storage for them.
> * Instead, the contained classes select the devices they need to attach
> * to via a matching function.
> */
> @@ -21,7 +21,8 @@
> #include "base.h"
>
> /* This is a private structure used to tie the classdev and the
> - * container .. it should never be visible outside this file */
> + * container .. it should never be visible outside this file
> + */
> struct internal_container {
> struct klist_node node;
> struct attribute_container *cont;
> @@ -449,7 +450,7 @@ attribute_container_remove_attrs(struct device *classdev)
>
> if (cont->grp) {
> sysfs_remove_group(&classdev->kobj, cont->grp);
> - return ;
> + return;
> }
>
> for (i = 0; attrs[i]; i++)
> --
> 2.47.1
>
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-03-01 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 18:27 [PATCH] drivers/base: fix iterator cleanup in attribute_container Ayaan Mirza Baig
2025-02-26 19:16 ` Greg KH
2025-02-27 12:41 ` [PATCH 1/2] drivers/base: fix checkpatch.pl warnings in attribute_container.c (v2) Ayaan Mirza Baig
2025-03-01 7:31 ` Greg KH [this message]
2025-02-27 12:41 ` [PATCH 2/2] drivers/base: fix iterator cleanup in attribute_container_find_class_device (v2) Ayaan Mirza Baig
2025-03-01 7:34 ` 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=2025022827-gesture-matted-d400@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ayaanmirza85@gmail.com \
--cc=ayaanmirzabaig85@gmail.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.