From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Pramod Maurya <pramod.nexgen@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] staging: rtl8723bs: Fix line over 100 chars in xmit_linux.c
Date: Wed, 3 Jun 2026 02:58:18 +0300 [thread overview]
Message-ID: <ah9uGi-BIE5RIVSs@ashevche-desk.local> (raw)
In-Reply-To: <20260523162831.163704-1-pramod.nexgen@gmail.com>
On Sat, May 23, 2026 at 12:28:31PM -0400, Pramod Maurya wrote:
> Wrap the long function signature of rtw_os_xmit_resource_free to
> comply with the 100 column line length limit reported by checkpatch.pl.
Folks, are you going to send a patch per a single issue (of the same type)?
It's quite extreme and puts tons of unnecessary load on maintainers and
reviewers. If you are fixing a problem (a type of problems) fix in the entire
driver at once. No need to go file-by-file.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-06-02 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 16:28 Pramod Maurya
2026-06-02 23:58 ` Andy Shevchenko [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=ah9uGi-BIE5RIVSs@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=pramod.nexgen@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
all inboxes | Powered by JetHome®