linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: module_license tree refreshed against linux-next
Date: Tue, 21 Mar 2023 10:29:08 +0000	[thread overview]
Message-ID: <87mt46s8i3.fsf@esperi.org.uk> (raw)

Just a note, now -rc3 is out and you might be considering looking at the
module-license stuff again: the current module_license tree at
https://github.com/nickalcock/linux module-license has been updated
against latest linux-next, upstreamed commits dropped, and all the
acked-bys/reviewed-bys I am aware of added. I've also introduced a few
more commits doing removals of MODULE_*, module.h inclusions etc where
maintainers have asked for it (but have not done that treewide).

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.

Test-built with make allyesconfig and allmodconfig (with clean tristate
checker runs) on x86-64: runs on aarch64 are underway. Not even tried
booting the result because booting an allyesconfig kernel is usually
troublesome even without linux-next in the mix :P

If you want a branch containing only those commits that have
acked-by/reviewed-by, I can do that, but it would have depressingly few
commits in (largely because most people who acked commits also took them
in, so I dropped them from my tree).

I hope my doing this makes your life a tiny bit easier!

             reply	other threads:[~2023-03-21 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 10:29 Nick Alcock [this message]
2023-03-21 16:32 ` module_license tree refreshed against linux-next Luis Chamberlain
2023-03-21 16:52   ` Nick Alcock
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=87mt46s8i3.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).