From: Nick Alcock <nick.alcock@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Nick Alcock <nick.alcock@oracle.com>,
dri-devel@lists.freedesktop.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-mm@kvack.org, linux-modules@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 00/17] MODULE_LICENSE removals, sixth tranche
Date: Mon, 20 Mar 2023 11:00:17 +0000 [thread overview]
Message-ID: <87ilevu1q6.fsf@esperi.org.uk> (raw)
In-Reply-To: <ZAJzCvTI67NgbJiY@bombadil.infradead.org> (Luis Chamberlain's message of "Fri, 3 Mar 2023 14:22:02 -0800")
(Sorry about this, MTA delivered a bunch of stuff very late.)
On 3 Mar 2023, Luis Chamberlain verbalised:
> Stupid question, if you're removing MODULE_LICENSE() than why keep the
> other stupid MODULE_*() crap too? If its of no use, be gone!
I wish, but when I tried it it broke stuff. At least some MODULE_ things
have side effects -- MODULE_DEVICE_TABLE, maybe MODULE_ALIAS etc...
... and also I was getting complaints when I sent a tree out that did
that, along the lines of "if MODULE_LICENSE is the problem why not just
remove that". It seems one cannot win here, both options elicit
complaints.
prev parent reply other threads:[~2023-03-20 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 21:17 Nick Alcock
2023-03-02 21:17 ` [PATCH 16/17] zpool: remove MODULE_LICENSE in non-modules Nick Alcock
2023-03-02 21:17 ` [PATCH 17/17] zswap: " Nick Alcock
2023-03-03 22:22 ` [PATCH 00/17] MODULE_LICENSE removals, sixth tranche Luis Chamberlain
2023-03-20 11:00 ` Nick Alcock [this message]
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=87ilevu1q6.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox