From: Greg KH <gregkh@linuxfoundation.org>
To: G Kranthi <kranthig55@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix line over 80 chars in ioctl_cfg80211.c
Date: Fri, 13 Mar 2026 07:21:54 +0100 [thread overview]
Message-ID: <2026031338-entering-fame-5806@gregkh> (raw)
In-Reply-To: <CAJ9fmhr=TFrfsw19Zj5n6DrgRTrOtGtFtymiGq5798UN0SKA5g@mail.gmail.com>
On Fri, Mar 13, 2026 at 09:52:30AM +0530, G Kranthi wrote:
> >From 38cf4de6f8d3946b71ba340864d673cfb58c74ac Mon Sep 17 00:00:00 2001
> From: Kranthi Gudisha <kranthi.gudisha@gmail.com>
> Date: Sat, 28 Feb 2026 22:57:25 +0530
> Subject: [PATCH] taging: rtl8723bs: fix line over 80 chars in ioctl_cfg80211.c
>
> Fix line exceeding 80 characters in function signature of
> rtw_cfg80211_add_monitor_if() by wrapping parameters to
> align with the open parenthesis.
>
> Signed-off-by: Kranthi Gudisha <kranthi.gudisha@gmail.com>
> ---
> drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> index a47d0d3fa2b7..75ce52498bb6 100644
> --- a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> +++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> @@ -2109,7 +2109,9 @@ static const struct net_device_ops
> rtw_cfg80211_monitor_if_ops = {
> .ndo_start_xmit = rtw_cfg80211_monitor_if_xmit_entry,
> };
>
> -static int rtw_cfg80211_add_monitor_if(struct adapter *padapter, char
> *name, struct net_device **ndev)
> +static int rtw_cfg80211_add_monitor_if(struct adapter *padapter,
> + char *name,
> + struct net_device **ndev)
> {
> int ret = 0;
> struct net_device *mon_ndev = NULL;
> --
> 2.34.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:
- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
and can not be applied. Please read the file,
Documentation/process/email-clients.rst in order to fix 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:[~2026-03-13 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 4:22 G Kranthi
2026-03-13 6:21 ` 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=2026031338-entering-fame-5806@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=kranthig55@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®