From: Madhumitha Prabakaran <madhumithabiw@gmail.com>
To: forest@alittletooquiet.net, gregkh@linuxfoundation.org,
outreachy-kernel@googlegroups.com
Cc: Madhumitha Prabakaran <madhumithabiw@gmail.com>
Subject: [PATCH v5 0/2] Fix checkpatch.pl issues
Date: Mon, 4 Mar 2019 11:00:51 -0600 [thread overview]
Message-ID: <cover.1551718323.git.madhumithabiw@gmail.com> (raw)
In-Reply-To: <cover.1551718323.git.madhumithabiw@gmail.com>
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
---
Changes in v5-
- Fixed subject lines for individual patches and versioned the patches
Changes in v4-
-Fixed matches in subject lines of the patches
Changes in v3-
- Fixed commit log and version number
Changes in v2-
-Included cover letter in patch set
drivers/staging/vt6655/channel.h | 2 +-
drivers/staging/vt6655/desc.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.17.1
next parent reply other threads:[~2019-03-04 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 17:00 Madhumitha Prabakaran [this message]
2019-03-04 17:00 ` [PATCH v5 1/2] Staging: vt6655: channel.h: Fix comment style of SPDX License Identifier Madhumitha Prabakaran
2019-03-04 17:00 ` [PATCH v5 2/2] Staging: vt6655: desc.h: Fix comment style of SPDX-License Identifier Madhumitha Prabakaran
2019-03-04 19:45 ` [PATCH v6 0/2] Fix checkpatch.pl issues Madhumitha Prabakaran
2019-03-04 19:45 ` [PATCH v6 1/2] Staging: vt6655: channel.h: Fix comment style of SPDX License Identifier Madhumitha Prabakaran
2019-03-04 19:45 ` [PATCH v6 2/2] Staging: vt6655: desc.h: Fix comment style of SPDX-License Identifier Madhumitha Prabakaran
-- strict thread matches above, loose matches on Subject: below --
2019-03-03 5:03 [PATCH v5 0/2] Fix checkpatch.pl issues Madhumitha Prabakaran
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=cover.1551718323.git.madhumithabiw@gmail.com \
--to=madhumithabiw@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--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.