From: Nick Alcock <nick.alcock@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: module_license tree refreshed against linux-next
Date: Tue, 21 Mar 2023 16:52:20 +0000 [thread overview]
Message-ID: <87r0tiqc6z.fsf@esperi.org.uk> (raw)
In-Reply-To: <ZBncDHaZfKEHAjGu@bombadil.infradead.org> (Luis Chamberlain's message of "Tue, 21 Mar 2023 09:32:12 -0700")
On 21 Mar 2023, Luis Chamberlain verbalised:
> On Tue, Mar 21, 2023 at 10:29:08AM +0000, Nick Alcock wrote:
>> I have not dropped commits with Greg K-H as maintainer simply because I
>> kept on oscillating on doing that, so I thought I'd leave the commits in
>> so you have the option to do either.
>
> No, I don't want to do that work, please drop Greg's drivers.
OK! Repushed to the same branch, sans what I *think* is the relevant set:
binder: remove MODULE_LICENSE in non-modules
serial: remove MODULE_LICENSE in non-modules
vgacon: remove MODULE_LICENSE in non-modules
tty: serial: imx: remove MODULE_LICENSE in non-modules
tty: remove MODULE_LICENSE in non-modules
I hope that's right -- it's all the patches he was directly Cc:ed on.
(other branches containing kallmodsyms as a whole, etc, have not yet
been refreshed at all and are old: I'll get to it).
next prev parent reply other threads:[~2023-03-21 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 10:29 module_license tree refreshed against linux-next Nick Alcock
2023-03-21 16:32 ` Luis Chamberlain
2023-03-21 16:52 ` Nick Alcock [this message]
2023-03-22 23:33 ` Luis Chamberlain
2023-03-23 16:45 ` Nick Alcock
2023-03-23 19:43 ` Luis Chamberlain
2023-03-23 20:00 ` Steven Rostedt
2023-03-23 20:38 ` Nick Alcock
2023-03-23 23:08 ` Steven Rostedt
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=87r0tiqc6z.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@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).