linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Spelvin <lkml@SDF.ORG>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Ajay.Kathat@microchip.com, linux-wireless@vger.kernel.org,
	devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
	johannes@sipsolutions.net, Adham.Abozaeid@microchip.com,
	lkml@sdf.org
Subject: Re: [PATCH v3] staging: wilc1000: Use crc7 in lib/ rather than a private copy
Date: Thu, 2 Apr 2020 15:30:34 +0000	[thread overview]
Message-ID: <20200402153034.GB2013@SDF.ORG> (raw)
In-Reply-To: <20200402082745.GG2001@kadam>

On Thu, Apr 02, 2020 at 11:27:45AM +0300, Dan Carpenter wrote:
> I don't know how this patch made it through two versions without anyone
> complaining that this paragraph should be done as a separate patch...

I often fold comment (and spacing/formatting) patches in to a main
patch, when touching adjacent code anyway and it doesn't cause
distracting clutter.

This seemed like such a case, which is why I submitted it as one.
But it's a bit of style thing.

>> Cc: Adham Abozaeid <adham.abozaeid@microchip.com>
>> Cc: linux-wireless@vger.kernel.org
>> Reviewed-by: Ajay Singh <ajay.kathat@microchip.com>
>> Signed-off-by: George Spelvin <lkml@sdf.org>
>> ---
> 
> This should have you Signed-off-by.  The Reviewed-by is kind of assumed
> so you can drop that bit.  But everyone who touches a patch needs to
> add their signed off by.

Er... all he did was add "staging: " to the front of the title.

That's not a change to the code at all, and as trivial a change
to the commit message as adding "Reviewed-by:" to the end.
We don't need S-o-b for such things or we'd end up in a horrible
infinite recursion.

  parent reply	other threads:[~2020-04-02 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 15:23 [PATCH v3] staging: wilc1000: Use crc7 in lib/ rather than a private copy Ajay.Kathat
2020-04-02  8:27 ` Dan Carpenter
2020-04-02 13:36   ` Ajay.Kathat
2020-04-02 15:30   ` George Spelvin [this message]
2020-04-03  9:10     ` Dan Carpenter
2020-04-03 23:40       ` George Spelvin
2020-04-04 10:05         ` Kalle Valo
2020-04-04 17:25         ` Dan Carpenter
2020-04-04 18:15           ` George Spelvin

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=20200402153034.GB2013@SDF.ORG \
    --to=lkml@sdf.org \
    --cc=Adham.Abozaeid@microchip.com \
    --cc=Ajay.Kathat@microchip.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).