From: Christoph Hellwig <hch@infradead.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
atomlin@atomlin.com, da.gomez@kernel.org,
linux-modules@vger.kernel.org, mcgrof@kernel.org,
petr.pavlu@suse.com, samitolvanen@google.com
Subject: Re: [PATCH v3] module: print version for external modules in print_modules()
Date: Tue, 10 Mar 2026 06:47:25 -0700 [thread overview]
Message-ID: <abAg7Wgq6N49pezT@infradead.org> (raw)
In-Reply-To: <CALOAHbCg=nmwtoaMJj1KpeGqAXEuuAdnW+RCbe5KXxKKYGozzA@mail.gmail.com>
On Tue, Mar 10, 2026 at 09:44:56PM +0800, Yafang Shao wrote:
> On Tue, Mar 10, 2026 at 9:43 PM Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Tue, Mar 10, 2026 at 09:35:23PM +0800, Yafang Shao wrote:
> > > > Why would that matter? You don't get a wild card to do things otherwise
> > > > rejected because you contributed something before.
> > >
> > > Could you please explain why I am being characterized as a "leecher"?
> >
> > Because you're adding overhead to the kernel for your out of tree code,
> > which only you and not the kernel project itself benefits from.
>
> Why do you believe the kernel project cannot benefit from them, given
> that all module maintainers have acknowledged their value?
Because by definition it does not benefit from making life for
out of tree modules easier. And I really don't get your whole
call to authority here, it makes hard for me to take you serious.
next prev parent reply other threads:[~2026-03-10 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 2:38 [PATCH v3] module: print version for external modules in print_modules() Yafang Shao
2026-03-10 6:31 ` Christoph Hellwig
2026-03-10 13:04 ` Yafang Shao
2026-03-10 13:07 ` Christoph Hellwig
2026-03-10 13:11 ` Yafang Shao
2026-03-10 13:14 ` Christoph Hellwig
2026-03-10 13:19 ` Yafang Shao
2026-03-10 13:21 ` Christoph Hellwig
2026-03-10 13:30 ` Yafang Shao
2026-03-10 13:33 ` Christoph Hellwig
2026-03-10 13:35 ` Yafang Shao
2026-03-10 13:43 ` Christoph Hellwig
2026-03-10 13:44 ` Yafang Shao
2026-03-10 13:47 ` Christoph Hellwig [this message]
2026-03-10 13:49 ` Yafang Shao
2026-03-11 22:44 ` Sami Tolvanen
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=abAg7Wgq6N49pezT@infradead.org \
--to=hch@infradead.org \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
/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