From: Michal Rostecki <vadorovsky@gmail.com>
To: Trevor Gross <tmgross@umich.edu>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@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@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Manmohan Shukla" <manmshuk@gmail.com>,
"Valentin Obst" <kernel@valentinobst.de>,
"Asahi Lina" <lina@asahilina.net>,
"Yutaro Ohno" <yutaro.ono.418@gmail.com>,
"Danilo Krummrich" <dakr@redhat.com>,
"Charalampos Mitrodimas" <charmitro@posteo.net>,
"Ben Gooding" <ben.gooding.dev@gmail.com>,
"Tejun Heo" <tj@kernel.org>, "Roland Xu" <mu001999@outlook.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
netdev@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3] rust: str: Use `core::CStr`, remove the custom `CStr` implementation
Date: Wed, 17 Jul 2024 17:10:06 +0200 [thread overview]
Message-ID: <0a4dd531-f075-4cce-9c15-30dfa1d0876d@gmail.com> (raw)
In-Reply-To: <CALNs47t=YQX+UP_ekq_Ue=BrA4JscDbU1qNDoKFar3yUbOSZ5g@mail.gmail.com>
On 16.07.24 02:45, Trevor Gross wrote:
> (also, v2 and v3 are appearing in different threads on lore (as they
> should), but they're in the same thread as v1 in my email client - any
> idea if there is a reason for this?)
No idea, I've sent both patches with:
git send-email --cc-cmd='./scripts/get_maintainer.pl --norolestats'
-v${VERSION} -1
prev parent reply other threads:[~2024-07-17 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 22:11 [PATCH v3] rust: str: Use `core::CStr`, remove the custom `CStr` implementation Michal Rostecki
2024-07-16 0:45 ` Trevor Gross
2024-07-17 15:10 ` Michal Rostecki [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=0a4dd531-f075-4cce-9c15-30dfa1d0876d@gmail.com \
--to=vadorovsky@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=ben.gooding.dev@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=charmitro@posteo.net \
--cc=dakr@redhat.com \
--cc=davidgow@google.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=justinstitt@google.com \
--cc=kernel@valentinobst.de \
--cc=kunit-dev@googlegroups.com \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=manmshuk@gmail.com \
--cc=morbo@google.com \
--cc=mu001999@outlook.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rmoar@google.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
--cc=yakoyoku@gmail.com \
--cc=yutaro.ono.418@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).