From: Danilo Krummrich <dakr@redhat.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@samsung.com,
aliceryhl@google.com, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] rust: str: add {make,to}_{upper,lower}case() to CString
Date: Tue, 12 Mar 2024 09:08:31 +0100 [thread overview]
Message-ID: <d0159c8c-f5d8-4731-a820-012702841bfc@redhat.com> (raw)
In-Reply-To: <CANiq72kK5CF0RQathACD_=7K1Ye4eMVdUnRcvkDZx4ALtq46wg@mail.gmail.com>
On 3/11/24 14:10, Miguel Ojeda wrote:
> On Mon, Mar 11, 2024 at 1:22 PM Danilo Krummrich <dakr@redhat.com> wrote:
>>
>> It doesn't seem there's any further feedback, thus can this be merged?
>
> No, it cannot be applied until the merge window closes, i.e. 2 weeks from now.
>
> Please note that there are other patches yet to be applied that were
> sent before this v5 -- we aim to send early PRs to Linus, and in
> general for at least a week in -next and for at least a week for
> review. Thus -rc5/6 is already quite late in general.
Thanks for sharing, that sounds all good. Just wanted to know if the
patch was queued up.
- Danilo
>
> Cheers,
> Miguel
>
next prev parent reply other threads:[~2024-03-12 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:37 [PATCH v5] rust: str: add {make,to}_{upper,lower}case() to CString Danilo Krummrich
2024-03-04 12:22 ` Danilo Krummrich
2024-03-11 12:22 ` Danilo Krummrich
2024-03-11 13:10 ` Miguel Ojeda
2024-03-12 8:08 ` Danilo Krummrich [this message]
2024-03-17 21:53 ` Miguel Ojeda
2024-03-15 11:47 ` Benno Lossin
2024-03-29 19:49 ` 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=d0159c8c-f5d8-4731-a820-012702841bfc@redhat.com \
--to=dakr@redhat.com \
--cc=a.hindborg@samsung.com \
--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=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=wedsonaf@gmail.com \
/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).