From: Greg KH <gregkh@linuxfoundation.org>
To: Ali Nasrolahi <a.nasrolahi01@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v3 0/2] staging: rtl8723bs: fix coding style issues
Date: Tue, 22 Jul 2025 09:37:05 +0200 [thread overview]
Message-ID: <2025072239-verdict-saloon-1263@gregkh> (raw)
In-Reply-To: <20250721164343.8395-1-A.Nasrolahi01@gmail.com>
On Mon, Jul 21, 2025 at 08:13:41PM +0330, Ali Nasrolahi wrote:
> This patch series addresses several coding style and comment formatting issues
> in the rtl8723bs staging driver as reported by checkpatch.pl.
>
> Thanks for your time and feedbacks
>
> Ali Nasrolahi (2):
> staging: rtl8723bs: fix comment formatting in basic_types.h
> staging: rtl8723bs: fix comment style and formatting in
> osdep_service.c
>
> drivers/staging/rtl8723bs/include/basic_types.h | 13 ++++++-------
> drivers/staging/rtl8723bs/os_dep/osdep_service.c | 11 ++++++-----
> 2 files changed, 12 insertions(+), 12 deletions(-)
>
> --
> 2.50.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 series,
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
prev parent reply other threads:[~2025-07-22 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 16:43 [PATCH v3 0/2] staging: rtl8723bs: fix coding style issues Ali Nasrolahi
2025-07-21 16:43 ` [PATCH v3 1/2] staging: rtl8723bs: fix comment formatting in basic_types.h Ali Nasrolahi
2025-07-22 7:37 ` Greg KH
2025-07-21 16:43 ` [PATCH v3 2/2] staging: rtl8723bs: fix comment style and formatting in osdep_service.c Ali Nasrolahi
2025-07-22 7:37 ` Greg KH
2025-07-22 7:37 ` Greg KH [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=2025072239-verdict-saloon-1263@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.nasrolahi01@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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