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:33:35 -0700 [thread overview]
Message-ID: <abAdr6zqeqSNMJ8X@infradead.org> (raw)
In-Reply-To: <CALOAHbBoX00_eDLq4X6vTrbdLG5X=9-07jW=Ba+Oa-QjtZX3MQ@mail.gmail.com>
On Tue, Mar 10, 2026 at 09:30:06PM +0800, Yafang Shao wrote:
> On Tue, Mar 10, 2026 at 9:21 PM Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Tue, Mar 10, 2026 at 09:19:22PM +0800, Yafang Shao wrote:
> > > Given that the Linux kernel officially supports out-of-tree modules,
> >
> > It does not officially support them as a first class entity.
>
> But out-of-tree modules are still a supported entity by the Linux
> kernel, correct?
They are not supported, and any support request that includes them is
typically rejected.
> > It adds overhead
>
> Could you please explain what overhead this might introduce?
It adds code that needs to be maintained and which is built into every
kernel.
>
> > to the kernel just for leechers like you that don't
> > actually contibute their code upstream. That's always a bad idea.
>
> I am not the GPU vendor, so I am unable to upstream the relevant code myself.
Well, that's not the kernels problem.
> By the way, here is a record of my contributions to the Linux kernel
> over the past few years:
Why would that matter? You don't get a wild card to do things otherwise
rejected because you contributed something before.
next prev parent reply other threads:[~2026-03-10 13:33 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 [this message]
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
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=abAdr6zqeqSNMJ8X@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