From: Thomas Gleixner <tglx@linutronix.de>
To: Tim Schumacher <timschumi@gmx.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: iforce - Remove empty multiline comments
Date: Mon, 8 Jul 2019 08:01:14 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1907080800160.3648@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190708025010.9318-1-timschumi@gmx.de>
On Mon, 8 Jul 2019, Tim Schumacher wrote:
> Those are remnants of the SPDX identifier migration, which haven't been
> removed properly.
>
> Signed-off-by: Tim Schumacher <timschumi@gmx.de>
> ---
> This is probably the highest level of cosmetic-only that a patch
> can achieve, sorry for the noise.
>
> CCing Thomas Gleixner, since the tool (is it a tool?) that makes
> those SPDX changes would have room for improvement in that regard.
> It seems to expect that all of the license information is contained
> within the same comment block, which wasn't the case for the iforce
> driver.
Right. I noticed too late, that these empty comments were left. Tool was
fixed for later patches.
Thanks for cleaning that up.
tglx
next prev parent reply other threads:[~2019-07-08 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 2:50 [PATCH] Input: iforce - Remove empty multiline comments Tim Schumacher
2019-07-08 6:01 ` Thomas Gleixner [this message]
2019-07-14 21:29 ` Dmitry Torokhov
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=alpine.DEB.2.21.1907080800160.3648@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=timschumi@gmx.de \
/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).