From: Nick Alcock <nick.alcock@oracle.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
jim.cromie@gmail.com, linux-modules@vger.kernel.org,
Aaron Tomlin <atomlin@redhat.com>,
Jason Baron <jbaron@akamai.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: RFC - KBUILD_MODNAME is misleading in builtins, as seen in /proc/dynamic_debug/control
Date: Tue, 21 Mar 2023 10:40:42 +0000 [thread overview]
Message-ID: <87edpis7yt.fsf@esperi.org.uk> (raw)
In-Reply-To: <CAK7LNASVpBih3iSHd=RXkKNZQ-v5LVzEOuZG3H_i3fcZfsGhDA@mail.gmail.com> (Masahiro Yamada's message of "Tue, 21 Mar 2023 18:03:01 +0900")
On 21 Mar 2023, Masahiro Yamada stated:
> He spams with MODULE_LICENSE removal with no justification.
Luis a) asked me to do it b) asked me to split it up like that (believe
me, it was extra work). A good few maintainers subsequently protested
that it wasn't split up even more finely.
I consider doing what Luis asks to constitute justification enough to
give it a try in this area -- or at least I'm not going to say no
without a damn good reason!
next prev parent reply other threads:[~2023-03-21 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 5:05 RFC - KBUILD_MODNAME is misleading in builtins, as seen in /proc/dynamic_debug/control jim.cromie
[not found] ` <6af9da81-7a7b-9f47-acb1-d0350bae7f3f@akamai.com>
2023-03-20 19:59 ` jim.cromie
2023-03-20 21:04 ` Luis Chamberlain
2023-03-21 9:03 ` Masahiro Yamada
2023-03-21 10:40 ` Nick Alcock [this message]
2023-03-21 16:31 ` Luis Chamberlain
2023-03-21 17:45 ` Nick Alcock
2023-03-21 6:45 ` Masahiro Yamada
2023-03-21 12:20 ` jim.cromie
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=87edpis7yt.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=atomlin@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@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