From: Kent Overstreet <kent.overstreet@linux.dev>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: TruongSinh Tran-Nguyen <i@truongsinh.pro>,
rust-for-linux@vger.kernel.org,
Wedson Almeida Filho <wedsonaf@gmail.com>,
linux-bcachefs@vger.kernel.org,
Andreas Hindborg <nmi@metaspace.dk>
Subject: Re: [PATCH] chore(util): minimal Rust build example
Date: Wed, 10 May 2023 14:38:11 -0400 [thread overview]
Message-ID: <ZFvkk9QUpIBTAIWj@moria.home.lan> (raw)
In-Reply-To: <CANiq72nYq5vimbhvfyUj9ejOS487LCQBxkv+7Nt5yYJ2xW_U-A@mail.gmail.com>
On Wed, May 10, 2023 at 07:59:03PM +0200, Miguel Ojeda wrote:
> On Wed, May 10, 2023 at 5:30 AM TruongSinh Tran-Nguyen <i@truongsinh.pro> wrote:
> >
> > I have another question. When working on user-space, I'm used to cargo
> > dependency management, but I assume it's not possible when doing
> > kernel development. Specifically, for the immediately next PR, I need
> > to use these 2 crates (and their artifacts)
>
> Please see https://rust-for-linux.com/third-party-crates (I just uploaded it).
Has cargo vendor been getting discussed?
next prev parent reply other threads:[~2023-05-10 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230503065354.19071-1-i@truongsinh.pro>
2023-05-09 17:47 ` [PATCH] chore(util): minimal Rust build example Kent Overstreet
2023-05-09 17:57 ` TruongSinh Tran-Nguyen
2023-05-09 18:12 ` Kent Overstreet
2023-05-09 18:41 ` Wedson Almeida Filho
2023-05-09 20:57 ` TruongSinh Tran-Nguyen
2023-05-10 3:10 ` TruongSinh Tran-Nguyen
2023-05-10 17:59 ` Miguel Ojeda
2023-05-10 18:21 ` TruongSinh Tran-Nguyen
2023-05-11 23:37 ` Miguel Ojeda
2023-05-11 23:54 ` TruongSinh Tran-Nguyen
2023-05-12 0:02 ` Miguel Ojeda
2023-05-12 3:31 ` Kent Overstreet
2023-05-12 4:16 ` TruongSinh Tran-Nguyen
2023-05-12 4:18 ` Kent Overstreet
2023-05-12 4:39 ` TruongSinh Tran-Nguyen
2023-05-12 5:33 ` Kent Overstreet
2023-05-12 14:26 ` TruongSinh Tran-Nguyen
2023-05-10 18:38 ` Kent Overstreet [this message]
2023-05-11 23:39 ` Miguel Ojeda
2023-05-11 16:16 ` Björn Roy Baron
2023-05-11 16:46 ` TruongSinh Tran-Nguyen
2023-05-11 17:05 ` Björn Roy Baron
2023-05-11 23:10 ` TruongSinh Tran-Nguyen
2023-05-09 20:52 ` Andreas Hindborg
2023-05-10 17:56 ` Miguel Ojeda
2023-05-10 18:44 ` Kent Overstreet
2023-05-11 23:37 ` 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=ZFvkk9QUpIBTAIWj@moria.home.lan \
--to=kent.overstreet@linux.dev \
--cc=i@truongsinh.pro \
--cc=linux-bcachefs@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nmi@metaspace.dk \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.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