From: Abdiel Janulgue <abdiel.janulgue@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org, aliceryhl@google.com,
dakr@redhat.com, linux-kernel@vger.kernel.org, lyude@redhat.com,
airlied@redhat.com, boqun.feng@gmail.com
Subject: Re: rust: page: Add support for vmalloc_to_page
Date: Tue, 8 Oct 2024 14:29:57 +0300 [thread overview]
Message-ID: <dc6faf9b-b44f-4c7b-82df-35e2eb0374ec@gmail.com> (raw)
In-Reply-To: <CANiq72=XBTi7eGE31m4qTWivGbD-du0qgRGhb6ZUOH28p=K_0Q@mail.gmail.com>
On 07/10/2024 23:58, Miguel Ojeda wrote:
> On Mon, Oct 7, 2024 at 10:28 PM Abdiel Janulgue
> <abdiel.janulgue@gmail.com> wrote:
>>
>> base-commit: 673d1648244c3840043e09a784164b38c2e2efb9
>
> Quick note: this is a `rust-next` commit, but this looks like it is
> meant to be on top of Danilo's `Allocator` series -- e.g. we don't
> have e.g. `VVec` there yet so it cannot build (but we will have that
> soon).
>
> By the way, cover letters normally go with [PATCH 0/...]. Since you
> have the base commit, I guess you used `--cover-letter` but changed
> the title maybe?
>
Sorry about that, my bad, I edited the cover by mistake. Will fix this
in next update.
Abdiel
> Thanks!
>
> Cheers,
> Miguel
prev parent reply other threads:[~2024-10-08 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 20:27 rust: page: Add support for vmalloc_to_page Abdiel Janulgue
2024-10-07 20:27 ` [PATCH 1/3] rust: page: replace the page pointer wrapper with Opaque Abdiel Janulgue
2024-10-08 6:58 ` Alice Ryhl
2024-10-08 7:04 ` Boqun Feng
2024-10-08 11:29 ` Abdiel Janulgue
2024-10-08 11:33 ` Boqun Feng
2024-10-11 11:07 ` Fiona Behrens
2024-10-15 13:21 ` Alice Ryhl
2024-10-07 20:27 ` [PATCH 2/3] rust: page: Extend support to vmalloc_to_page Abdiel Janulgue
2024-10-07 20:27 ` [PATCH 3/3] rust: page: Add page_slice_to_page Abdiel Janulgue
2024-10-11 11:03 ` kernel test robot
2024-10-07 20:58 ` rust: page: Add support for vmalloc_to_page Miguel Ojeda
2024-10-08 11:29 ` Abdiel Janulgue [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=dc6faf9b-b44f-4c7b-82df-35e2eb0374ec@gmail.com \
--to=abdiel.janulgue@gmail.com \
--cc=airlied@redhat.com \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).