rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tamir Duberstein <tamird@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Danilo Krummrich" <dakr@kernel.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,
	"Alejandro Colomar" <alx@kernel.org>
Subject: Re: [PATCH v3] rust: allocator_test: use `posix_memalign`
Date: Fri, 7 Feb 2025 12:23:55 -0500	[thread overview]
Message-ID: <CAJ-ks9nFo7broCoOSBzzaG1uHEK=Lch8vxhGCvqQj4xwWP0nXQ@mail.gmail.com> (raw)
In-Reply-To: <CANiq72=P3O5Q=S4JBVGY0B0t5xSfMYGu3YbhT6SQmbVcAkEA8A@mail.gmail.com>

On Fri, Feb 7, 2025 at 7:19 AM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Fri, Feb 7, 2025 at 12:43 PM Tamir Duberstein <tamird@gmail.com> wrote:
> >
> > I'm happy to wait for clarification, I'm just not sure whose court the
> > ball is in.
>
> Ideally Alejandro would clarify, who I Cc'd in the previous thread (he
> was not Cc'd here, by the way).

Sorry about that.

> Anyway, I agree with Danilo that we shouldn't overcomplicate just for
> this. Using the previous patch, but being clear about that we are
> using stricter requirements so that it works on macOS too, should be
> fine I think. But I trust Danilo to decide which approach is best for
> maintaining this.
>
> Cheers,
> Miguel

Seems there's consensus on the previous patch. I've reworded it and
will send it in v4 next week to allow Alejandro some time to weigh in.

Thanks.
Tamir

      reply	other threads:[~2025-02-07 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 20:49 [PATCH v3] rust: allocator_test: use `posix_memalign` Tamir Duberstein
2025-02-06 21:56 ` Danilo Krummrich
2025-02-07 11:43   ` Tamir Duberstein
2025-02-07 12:19     ` Miguel Ojeda
2025-02-07 17:23       ` Tamir Duberstein [this message]

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='CAJ-ks9nFo7broCoOSBzzaG1uHEK=Lch8vxhGCvqQj4xwWP0nXQ@mail.gmail.com' \
    --to=tamird@gmail.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=alx@kernel.org \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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;
as well as URLs for NNTP newsgroup(s).