From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arm-soc <arm@kernel.org>
Subject: Re: [PATCH] ARM: pxa/tosa-bt: add MODULE_LICENSE tag
Date: Fri, 19 Jan 2018 18:18:53 +0100 [thread overview]
Message-ID: <87bmhpahs2.fsf@belgarion.home> (raw)
In-Reply-To: <CAK8P3a1VeN0kLrJ5T57y46NR1GNviwZ=6baaXgSm9ZqYBnGuVA@mail.gmail.com> (Arnd Bergmann's message of "Fri, 19 Jan 2018 17:02:25 +0100")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, Jan 10, 2018 at 9:22 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
>> Arnd Bergmann <arnd@arndb.de> writes:
>>
>>> Without this tag, we get a build warning:
>>>
>>> WARNING: modpost: missing MODULE_LICENSE() in arch/arm/mach-pxa/tosa-bt.o
>>>
>>> For completeness, I'm also adding author and description fields.
>>>
>>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>>
>> Queued into pxa/for-next, thanks.
>
> I see now that you didn't send this back to arm@kernel.org. I assume you planned
> to send it for 4.17, but kernelci now still reports the warning for
> both 4.15 and
> linux-next (4.16). Should we just include this patch in the 4.16 fixes
> instead?
Yeah sure, go ahead and merge it into 4.16 staging branch, with my :
Acked-by: Robert Jarzmik <robert.jarzmik@free.fr>
Cheers.
--
Robert
next prev parent reply other threads:[~2018-01-19 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 16:28 [PATCH] ARM: pxa/tosa-bt: add MODULE_LICENSE tag Arnd Bergmann
2018-01-10 20:22 ` Robert Jarzmik
2018-01-19 16:02 ` Arnd Bergmann
2018-01-19 17:18 ` Robert Jarzmik [this message]
2018-01-22 11:36 ` Arnd Bergmann
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=87bmhpahs2.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).