From: Yury Norov <yury.norov@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Burak Emir" <bqe@google.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: adds bindings for bitmap.c and bitops.c
Date: Wed, 19 Mar 2025 12:06:56 -0400 [thread overview]
Message-ID: <Z9rroCn3MAsXz1Lw@thinkpad> (raw)
In-Reply-To: <CANiq72k8-5YRwmcn1h+avuyusAC36ttOqwsMH_eO-DLxTm5gpw@mail.gmail.com>
On Wed, Mar 19, 2025 at 04:43:50PM +0100, Miguel Ojeda wrote:
> On Wed, Mar 19, 2025 at 2:58 PM Burak Emir <bqe@google.com> wrote:
> >
> > Thanks, I was unsure about this. I understand the desire to not add dead code.
> > Yet, next-20250318 does now contain helpers for `cpumask.c` without
> > corresponding `cpumask.rs`
> >
> > So, I will include this in v5 of the rebased series, but with BITOPS
> > API BINDINGS [RUST] in its own patch.
> > Thanks for bearing with me : )
>
> No worries at all! Perhaps wait a bit in case I misunderstood and Yury
> wants to clarify.
Yes, the general idea is to be able look through the all software pieces
in a single series - from C wrappers all the way down to rust end users.
This way I'll make sure you are using the API in a right way. And I
think I already helped you in that department, right?
next prev parent reply other threads:[~2025-03-19 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 11:27 [PATCH] rust: adds bindings for bitmap.c and bitops.c Burak Emir
2025-03-19 12:46 ` Miguel Ojeda
2025-03-19 13:58 ` Burak Emir
2025-03-19 15:43 ` Miguel Ojeda
2025-03-19 16:06 ` Yury Norov [this message]
2025-03-19 16:11 ` Burak Emir
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=Z9rroCn3MAsXz1Lw@thinkpad \
--to=yury.norov@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bqe@google.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.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.