From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Joe Perches <joe@perches.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] checkpatch: Add test for SPDX-License-Identifier on wrong line #
Date: Mon, 11 Feb 2019 13:41:43 +0100 [thread overview]
Message-ID: <e64adaf7-d7e2-76b7-cfe3-0cbb5c32c79d@metux.net> (raw)
In-Reply-To: <9b74ee87f8c1b8fd310e213fcb4994d58610fcb6.camel@perches.com>
On 08.02.19 21:44, Joe Perches wrote:
> Warn when any SPDX-License-Identifier: tag is not created
> on the proper line number.
By the way: there are corner cases, which can't have it at the first
line, eg. scripts.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-02-11 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 1:16 [PATCH 1/2] x86: gpio: AMD G-Series pch gpio platform driver Enrico Weigelt, metux IT consult
2019-02-08 1:16 ` [PATCH 2/2] x86: pcengines apuv2 gpio/leds/keys " Enrico Weigelt, metux IT consult
2019-02-08 14:30 ` Linus Walleij
2019-02-08 15:21 ` Andy Shevchenko
2019-02-11 10:38 ` Enrico Weigelt, metux IT consult
2019-02-13 9:35 ` Linus Walleij
2019-02-14 10:57 ` Enrico Weigelt, metux IT consult
2019-02-08 14:25 ` [PATCH 1/2] x86: gpio: AMD G-Series pch gpio " Linus Walleij
2019-02-08 15:20 ` Andy Shevchenko
2019-02-08 17:47 ` Joe Perches
2019-02-08 20:44 ` [PATCH] checkpatch: Add test for SPDX-License-Identifier on wrong line # Joe Perches
2019-02-11 12:41 ` Enrico Weigelt, metux IT consult [this message]
2019-02-11 12:49 ` Joe Perches
2019-02-11 10:46 ` [PATCH 1/2] x86: gpio: AMD G-Series pch gpio platform driver Enrico Weigelt, metux IT consult
2019-02-13 9:02 ` Linus Walleij
2019-02-14 9:53 ` Enrico Weigelt, metux IT consult
2019-02-14 9:56 ` Enrico Weigelt, metux IT consult
2019-02-20 9:37 ` Linus Walleij
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=e64adaf7-d7e2-76b7-cfe3-0cbb5c32c79d@metux.net \
--to=lkml@metux.net \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®