From: Dan Carpenter <dan.carpenter@linaro.org>
To: Mariyam Shahid <mariyam.shahid135@gmail.com>
Cc: gregkh@linuxfoundation.org, straube.linux@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Wrap long comments to fit line length
Date: Thu, 26 Feb 2026 13:51:49 +0300 [thread overview]
Message-ID: <aaAlxYSqSaHtIDIq@stanley.mountain> (raw)
In-Reply-To: <20260226103120.32230-1-mariyam.shahid135@gmail.com>
On Thu, Feb 26, 2026 at 03:31:20PM +0500, Mariyam Shahid wrote:
> Wrap comments exceeding 100 columns across multiple lines
> to fix checkpatch warnings.
>
Not even one of these changes has to do with the 100 character limit.
Please, split them up so you fix one type of warning per patch.
regards,
dan carpenter
next prev parent reply other threads:[~2026-02-26 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 10:31 [PATCH] staging: rtl8723bs: Wrap long comments to fit line length Mariyam Shahid
2026-02-26 10:51 ` Dan Carpenter [this message]
2026-02-27 7:25 ` Mariyam Shahid
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=aaAlxYSqSaHtIDIq@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mariyam.shahid135@gmail.com \
--cc=straube.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox