From: Nicolas Schier <nicolas@fjasle.eu>
To: "Daniel Walker (danielwa)" <danielwa@cisco.com>
Cc: Nicolas Schier <n.schier@avm.de>,
"Valerii Chernous -X (vchernou - GLOBALLOGIC INC at Cisco)"
<vchernou@cisco.com>, Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Add MO(mod objs) variable to process ext modules with subdirs
Date: Thu, 11 Apr 2024 21:25:35 +0200 [thread overview]
Message-ID: <Zhg5L2xO_lT4lLwp@fjasle.eu> (raw)
In-Reply-To: <ZhgdjpE+yl3IYSzl@goliath>
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
On Thu, Apr 11, 2024 at 05:27:42PM +0000 Daniel Walker (danielwa) wrote:
> On Thu, Apr 11, 2024 at 01:38:20PM +0200, Nicolas Schier wrote:
> > Hi Valerii,
> >
> > thanks for your patch. I know several non-upstream kernel developers
> > that would like to see support for out-of-source builds of external
> > kmods (and we developed several work-arounds at AVM as well); but please
> > be aware that patches that don't fix or enhance the in-tree kernel/kmod
> > build but only add feature for out-of-tree stuff, are rarely accepted.
"out-of-tree stuff" was meant to be "out-of-tree kernel modules". "Rarely" was
chosen in explicit contrast to "never", but to hint on my personal expectation
regarding the probability of acceptance.
> If that were true we would not have driver/uio/ for example. It seems like
> Cisco and NVM should work together produce a solution.
>
> You could run into this issue even with entirely in tree modules. For example,
> we may have a v6.6 kernel but we need some modules from v5.15 for some incompatibility
> reason in v6.6. Then we may build the v5.15 modules as out of tree modules
> against the v6.6 kernel.
If your in-tree module in question does compile and run properly in v5.15 and
in v6.6: why don't you just compile it in-tree in v6.6? Which driver/module do
you refer to?
> You also have just normal developers making kernel modules which always start as
> out of tree modules before they are upstreamed. Those modules could be any level
> of complexity.
I do not agree, but there is no need to convince me as I am not in the position
to decide between acceptance or denial. I just thought it might be fair to
warn that I do not expect acceptance.
Kind regards,
Nicolas
> I don't think it make sense to view this as strictly enhancing large of the tree
> modules with no upstream potential.
>
> Daniel
--
epost|xmpp: nicolas@fjasle.eu irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f
-- frykten for herren er opphav til kunnskap --
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-11 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 16:56 [PATCH v3] Add MO(mod objs) variable to process ext modules with subdirs Valerii Chernous
2024-04-05 17:19 ` Randy Dunlap
2024-04-11 11:38 ` Nicolas Schier
2024-04-11 17:27 ` Daniel Walker (danielwa)
2024-04-11 19:25 ` Nicolas Schier [this message]
2024-04-11 20:50 ` Daniel Walker (danielwa)
2024-04-12 6:34 ` Nicolas Schier
2024-04-12 15:01 ` Daniel Walker (danielwa)
[not found] ` <DS0PR11MB77652A4C98FCB671F5E5F3EEDE042@DS0PR11MB7765.namprd11.prod.outlook.com>
2024-04-12 9:46 ` Valerii Chernous -X (vchernou - GLOBALLOGIC INC at Cisco)
2024-04-14 8:48 ` Masahiro Yamada
2024-04-15 10:21 ` Valerii Chernous -X (vchernou - GLOBALLOGIC INC at Cisco)
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=Zhg5L2xO_lT4lLwp@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=corbet@lwn.net \
--cc=danielwa@cisco.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=n.schier@avm.de \
--cc=nathan@kernel.org \
--cc=vchernou@cisco.com \
--cc=xe-linux-external@cisco.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