From: Sven Eckelmann <sven@narfation.org>
To: Joe Perches <joe@perches.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [patch 2/2] scripts/spdxcheck.py: Handle special quotation mark comments
Date: Wed, 06 Feb 2019 19:50:17 +0100 [thread overview]
Message-ID: <20661651.ZxqjWeeW99@sven-edge> (raw)
In-Reply-To: <d9eb35b2594d9cfedd8525dc32a18b40c60451b0.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
On Sunday, 20 January 2019 19.39.55 CET Joe Perches wrote:
> Well, maybe checkpatch should remove the comment trailer.
> ---
> Miscellanea:
In case you are waiting for me (haven't seen it popping up in linux-next):
yes, this patch solves the problem for me.
Tested-by: Sven Eckelmann <sven@narfation.org>
Thanks,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-06 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 10:26 [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions Thomas Gleixner
2019-01-16 10:26 ` [patch 1/2] LICENSES: Add GCC runtime library exception text Thomas Gleixner
2019-01-16 15:36 ` Greg Kroah-Hartman
2019-01-16 10:26 ` [patch 2/2] scripts/spdxcheck.py: Handle special quotation mark comments Thomas Gleixner
2019-01-16 15:38 ` Greg Kroah-Hartman
2019-01-20 15:32 ` Sven Eckelmann
2019-01-20 18:39 ` Joe Perches
2019-02-06 18:50 ` Sven Eckelmann [this message]
2019-01-16 21:56 ` [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions Jonathan Corbet
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=20661651.ZxqjWeeW99@sven-edge \
--to=sven@narfation.org \
--cc=akpm@linux-foundation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=corbet@lwn.net \
--cc=dalias@libc.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=joe@perches.com \
--cc=kstewart@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ysato@users.sourceforge.jp \
/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®