Rust for Linux List
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: TruongSinh Tran-Nguyen <i@truongsinh.pro>
Cc: linux-bcachefs@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] chore(util): minimal Rust build example
Date: Tue, 9 May 2023 14:12:00 -0400	[thread overview]
Message-ID: <ZFqM8HOvlVn61VXs@moria.home.lan> (raw)
In-Reply-To: <CAMy36z75N9obj0WM+OFhhnzXAPxqhg8PVY7_x8X6JbQABFnMQw@mail.gmail.com>

On Tue, May 09, 2023 at 10:57:18AM -0700, TruongSinh Tran-Nguyen wrote:
> On Tue, 9 May 2023 at 10:47, Kent Overstreet <kent.overstreet@linux.dev> wrote:
> 
> > We pretty heavily use to_text() functions kernel side; these output to
> > printbufs, and in Rust they map nicely to the Display trait - do we have
> > that available in the kernel or is that in std?
> >
> 
> https://doc.rust-lang.org/std/fmt/trait.Display.html Display trait is definitely
> in Rust `std`. As for the alternative from kernel, I am still searching.
> Worst case, there is nothing right now, Rust-for-linux folks would
> happy to take PR
> to include it.

I included them on the CC, maybe they'll have something to say.

> 
> > Sounds like that would be a welcome cleanup :)
> 
> By clean up, do you mean moving from `uuid_le` to `uuid_t`?
> 
> Also, I don't expect this PR to be merge, as it is for demonstration
> purposes only,
> however, what would be a minimum mergeable PR (related to Rust build)
> that you would consider?

First thing to look at is going to be moving all the code under
bch_bindgen in -tools into the kernel tree...

  reply	other threads:[~2023-05-09 18:13 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 [this message]
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
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=ZFqM8HOvlVn61VXs@moria.home.lan \
    --to=kent.overstreet@linux.dev \
    --cc=i@truongsinh.pro \
    --cc=linux-bcachefs@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox