archive mirror
 help / color / mirror / Atom feed
From: Hanqing Zhao <>
To: Miguel Ojeda <>
Cc: rust-for-linux <>
Subject: Re: [Question] import third-party crates in kernel modules
Date: Mon, 26 Apr 2021 16:41:04 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Sounds good.

I'll manually replicate them tentatively.

After I finish the linux kernel integration, I'll show my
demonstration to the rust-linux community.

Hanqing Zhao
Georgia Tech

On Mon, Apr 26, 2021 at 4:20 PM Miguel Ojeda
<> wrote:
> On Mon, Apr 26, 2021 at 9:10 PM Hanqing Zhao <> wrote:
> >
> > I am actually writing a new alloc crate for linux kernel.
> Please note that we are still evaluating how to approach this. The
> best way to get involved with high-level design is to join the
> meetings.
> > I think it would be better if we can import 3rd-party crates while
> > developing and testing our own kernel modules,
> > i.e., we do not need to guarantee that the kernel module having
> > 3rd-party dependencies can become an in-tree module,
> > but we can compile a .ko that has a 3rd-part dependency
> > during offline development and testing.
> We need whatever infrastructure is required to be available for
> in-tree modules too (and we need to focus on those first). A lot of
> things are missing, indeed, but we will get there!
> Meanwhile, perhaps you can manually import them as a workaround -- I
> understand that missing functionality can be a bit painful.
> Cheers,
> Miguel

  reply	other threads:[~2021-04-26 20:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 17:01 [Question] import third-party crates in kernel modules Hanqing Zhao
2021-04-26 18:32 ` Miguel Ojeda
2021-04-26 19:10   ` Hanqing Zhao
2021-04-26 20:20     ` Miguel Ojeda
2021-04-26 20:41       ` Hanqing Zhao [this message]
2021-04-26 23:16         ` Miguel Ojeda
2021-04-27  1:28         ` Wedson Almeida Filho
2021-04-26 23:54       ` Kajetan Puchalski
2021-04-27  0:36         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).