From: Alex Gaynor <alex.gaynor@gmail.com>
To: "Nándor Krácser" <bonifaido@gmail.com>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Using 3rd party crates in an out-of-tree module
Date: Mon, 21 Mar 2022 10:36:40 -0400 [thread overview]
Message-ID: <CAFRnB2W+8XqOj0aL5DP2cMNLO2uR0DpPk-qB-oC7r=zT5N5gGA@mail.gmail.com> (raw)
In-Reply-To: <CAHkG_ewRo5uPOue3ZMAAPAc+eP7MNNU5iVym-JVG1jN7HD+XMg@mail.gmail.com>
Hi Nándor,
That's correct that there's currently no support for pulling in 3rd
party modules automatically with cargo. This is because any work that
goes into the upstream kernel will need to be self-contained to the
maximum extent possible.
I don't know if anyone has given any thought to supporting 3rd party
crates for out-of-tree modules.
Alex
On Mon, Mar 21, 2022 at 10:12 AM Nándor Krácser <bonifaido@gmail.com> wrote:
>
> Hi,
>
> I was looking at the out-of-tree example at
> https://github.com/Rust-for-Linux/rust-out-of-tree-module and found
> myself in a situation where I wanted to pull in a 3rd party module
> from crates.io which can run in kernel space as well. How can this be
> done?
>
> As far as I know there is no cargo support currently in the Makefiles,
> but maybe I'm missing something.
>
> Thank you!
>
> Nándor István Krácser
> bonifaido@gmail.com
--
All that is necessary for evil to succeed is for good people to do nothing.
next prev parent reply other threads:[~2022-03-21 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 9:40 Using 3rd party crates in an out-of-tree module Nándor Krácser
2022-03-21 14:36 ` Alex Gaynor [this message]
2022-03-21 23:14 ` Miguel Ojeda
2022-03-23 9:40 ` Nándor Krácser
2022-03-23 11:40 ` Greg KH
2022-03-21 16:49 ` Miguel Ojeda
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='CAFRnB2W+8XqOj0aL5DP2cMNLO2uR0DpPk-qB-oC7r=zT5N5gGA@mail.gmail.com' \
--to=alex.gaynor@gmail.com \
--cc=bonifaido@gmail.com \
--cc=rust-for-linux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.