From: Nitesh Lal <nilal@redhat.com>
To: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Cc: linux-tip-commits@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
x86@kernel.org
Subject: Re: [tip: timers/core] time/kunit: Add missing MODULE_LICENSE()
Date: Sun, 27 Jun 2021 14:24:46 -0400 [thread overview]
Message-ID: <CAFki+Lmu5ARgqYFxtFho+sUke9eg9=ZMTQbA1JVoJQqGeYRd5g@mail.gmail.com> (raw)
In-Reply-To: <162474059066.395.17544610641097100087.tip-bot2@tip-bot2>
On Sat, Jun 26, 2021 at 4:51 PM tip-bot2 for Thomas Gleixner
<tip-bot2@linutronix.de> wrote:
>
> The following commit has been merged into the timers/core branch of tip:
>
> Commit-ID: 34c7342ac1b4e496315fb615d2a1309df8400403
> Gitweb: https://git.kernel.org/tip/34c7342ac1b4e496315fb615d2a1309df8400403
> Author: Thomas Gleixner <tglx@linutronix.de>
> AuthorDate: Sat, 26 Jun 2021 22:44:11 +02:00
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitterDate: Sat, 26 Jun 2021 22:47:32 +02:00
>
> time/kunit: Add missing MODULE_LICENSE()
>
> Reported-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> kernel/time/time_test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/time/time_test.c b/kernel/time/time_test.c
> index 341ebfa..a064a7c 100644
> --- a/kernel/time/time_test.c
> +++ b/kernel/time/time_test.c
> @@ -96,3 +96,4 @@ static struct kunit_suite time_test_suite = {
> };
>
> kunit_test_suite(time_test_suite);
> +MODULE_LICENSE(GPL);
>
This should be:
MODULE_LICENSE("GPL");
isn't it?
We will get a compilation error otherwise.
--
Thanks
Nitesh
next prev parent reply other threads:[~2021-06-27 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 20:49 [tip: timers/core] time/kunit: Add missing MODULE_LICENSE() tip-bot2 for Thomas Gleixner
2021-06-27 18:24 ` Nitesh Lal [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-28 5:46 tip-bot2 for Thomas Gleixner
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='CAFki+Lmu5ARgqYFxtFho+sUke9eg9=ZMTQbA1JVoJQqGeYRd5g@mail.gmail.com' \
--to=nilal@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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.