From: Larry Finger <Larry.Finger@lwfinger.net>
To: Parth Sane <laerdevstudios@gmail.com>, gregkh@linuxfoundation.org
Cc: florian.c.schilhabel@googlemail.com, amitoj1606@gmail.com,
luisbg@osg.samsung.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8712: Removed FSF address warning
Date: Sun, 20 Mar 2016 09:26:10 -0500 [thread overview]
Message-ID: <56EEB302.3050903@lwfinger.net> (raw)
In-Reply-To: <1458482397-1599-1-git-send-email-laerdevstudios@gmail.com>
On 03/20/2016 08:59 AM, Parth Sane wrote:
> Removed checkpatch warning caused by FSF address block
> Signed-off-by: Parth Sane <laerdevstudios@gmail.com>
> ---
> drivers/staging/rtl8712/hal_init.c | 4 ----
> 1 file changed, 4 deletions(-)
Now you have at least 3 different patches all with the same subject! How is the
maintainer supposed to keep them separate? Patchworks will replace each of them
with the next one having the same title.
A better way would be to create a multiple-part set of patches with the subject
containing the name of the file being "fixed".
Note that this warning was added to checkpatch.pl well after the driver was
added to the staging tree. In fact, if this warning had been present then, the
FSF address would have been removed.
I consider this type of patch to be of minimal value; however, if you do not
remove this warning, then someone else will. Thus, you should repackage these
changes. By my count, there are 94 files containing this information. Dropping
them as one set of patches might be too many at once. I would split them into
groups of 13 files in one batch, 14 in the next, then 15, 16, 17, and finally
19, then each group will also be distinguishable.
If GregKH wants it done differently, he will let us know.
Larry
next prev parent reply other threads:[~2016-03-20 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 13:59 [PATCH] staging: rtl8712: Removed FSF address warning Parth Sane
2016-03-20 14:26 ` Larry Finger [this message]
2016-03-20 14:58 ` Parth Sane
-- strict thread matches above, loose matches on Subject: below --
2016-03-20 14:13 Parth Sane
2016-03-20 14:07 Parth Sane
2016-03-20 13:42 Parth Sane
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=56EEB302.3050903@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=amitoj1606@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=laerdevstudios@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.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