All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Madhumitha Prabakaran <madhumithabiw@gmail.com>
Cc: forest@alittletooquiet.net, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v4 0/2] Fix checkpatch.pl issues
Date: Sat, 2 Mar 2019 22:18:50 +0100	[thread overview]
Message-ID: <20190302211850.GA21688@kroah.com> (raw)
In-Reply-To: <cover.1551552831.git.madhumithabiw@gmail.com>

On Sat, Mar 02, 2019 at 01:04:25PM -0600, Madhumitha Prabakaran wrote:
> This patchset fixes the comment styles of SPDX-License Identifier based
> on License Identifier syntax.
> 
> Madhumitha Prabakaran (2):
>   Staging: vt6655: channel.h: Fix comment style of SPDX License Identifier
>   Staging: vt6655: desc.h: Fix comment style of SPDX License Identifier

Again, these look fine.

Now go look at the subject lines of the patches you sent out.  It does
not match these.

Something is really wrong with either how you are generating this
message, or the patches, it does not make sense at all.  They should
always match up identically as git should do it all for you.

Please try sending the series to only yourself next, to verify you got
it right, before sending it to everyone.

thanks,

greg k-h


  parent reply	other threads:[~2019-03-02 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 19:04 [PATCH v4 0/2] Fix checkpatch.pl issues Madhumitha Prabakaran
2019-03-02 19:04 ` [PATCH v4 1/2] Staging: vt6655: Fix comment style of SPDX License Identifier Madhumitha Prabakaran
2019-03-02 19:04 ` [PATCH v4 2/2] " Madhumitha Prabakaran
2019-03-02 21:18 ` Greg KH [this message]
2019-03-03  2:06   ` [PATCH v4 0/2] Fix checkpatch.pl issues Madhumthia Prabakaran
2019-03-03  5:21   ` Madhumthia Prabakaran
2019-03-03  6:16     ` [Outreachy kernel] " Julia Lawall

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=20190302211850.GA21688@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=forest@alittletooquiet.net \
    --cc=madhumithabiw@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.