public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bertschinger <tahbertschinger@gmail.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, bfoster@redhat.com
Subject: Re: [PATCH TOOLS 0/2] convert main() from C to Rust
Date: Mon, 15 Jan 2024 12:10:22 -0700	[thread overview]
Message-ID: <20240115191022.GC156208@fedora-laptop> (raw)
In-Reply-To: <iiraqelv6wtwxcdf2yjtjt26ghejngfantjx7d4mztav27qu7y@gmiztxamveq3>

On Mon, Jan 15, 2024 at 01:45:22PM -0500, Kent Overstreet wrote:
> On Mon, Jan 15, 2024 at 10:55:09AM -0700, Thomas Bertschinger wrote:
> > I'm leaning towards keeping Make as the primary build tool for now and
> > perhaps a future patch can move towards using Cargo. But other opinions
> > are welcome.
> 
> Let's hold off on that for now.
> 
> I'm planning on pullling the Rust code in bch_bindgen into the kernel
> soon, and I want to see how that interacts with the kernel build system.
> If there's potential for commonality with the kernel build system, we
> might want to take advantage of that.
> 
> (Also, if you're interested in that project, let me know! Getting that
> ready for the next merge window is a high priority item, but I have a
> lot of high priority items at the moment... :)

Sure, I would definitely be interested in helping out with that. I don't
want to make any promises regarding timeline, since this combines two
worlds--Rust, and Linux Kernel development--that are both still very
new to me. But I can certainly give it an honest try :) as long as you,
or someone else experienced, can help with any questions I might run
into.

  reply	other threads:[~2024-01-15 19:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  5:24 [PATCH TOOLS 0/2] convert main() from C to Rust Thomas Bertschinger
2024-01-15  5:24 ` [PATCH TOOLS 1/2] " Thomas Bertschinger
2024-01-15  5:24 ` [PATCH TOOLS 2/2] remove library from bcachefs-tools Rust package Thomas Bertschinger
2024-01-15 17:32 ` [PATCH TOOLS 0/2] convert main() from C to Rust Kent Overstreet
2024-01-15 17:55   ` Thomas Bertschinger
2024-01-15 18:45     ` Kent Overstreet
2024-01-15 19:10       ` Thomas Bertschinger [this message]
2024-01-15 19:22         ` Kent Overstreet
2024-01-19 19:05           ` Trevor Gross
2024-01-19 21:37             ` Kent Overstreet
2024-01-21 16:11               ` packed, aligned structs in bcachefs (was: Re: [PATCH TOOLS 0/2] convert main() from C to Rust) Thomas Bertschinger
2024-01-21 18:19                 ` Kent Overstreet
2024-01-21 19:32                   ` Thomas Bertschinger
2024-01-22  2:47                     ` Thomas Bertschinger
2024-01-15 17:48 ` [PATCH TOOLS 0/2] convert main() from C to Rust Kent Overstreet
2024-01-15 17:57   ` Thomas Bertschinger

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=20240115191022.GC156208@fedora-laptop \
    --to=tahbertschinger@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@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