From: Alice Ryhl <aliceryhl@google.com>
To: ariel.miculas@gmail.com
Cc: alex.gaynor@gmail.com, asahi@lists.linux.dev,
benno.lossin@proton.me, bjorn3_gh@protonmail.com,
boqun.feng@gmail.com, gary@garyguo.net, lina@asahilina.net,
linux-kernel@vger.kernel.org, ojeda@kernel.org,
rust-for-linux@vger.kernel.org, wedsonaf@gmail.com
Subject: Re: [PATCH] rust: kernel: str: Implement Debug for CString
Date: Fri, 14 Jul 2023 14:02:01 +0000 [thread overview]
Message-ID: <20230714140201.383439-1-aliceryhl@google.com> (raw)
In-Reply-To: <CAPDJoNv1HW-5uCj21PX3t23rJ+sbTL4Gm5pDis8HGJ-VTr4dug@mail.gmail.com>
Asahi Lina <lina@asahilina.net> writes:
> On 14/07/2023 18.48, Alice Ryhl wrote:
>> Asahi Lina <lina@asahilina.net> writes:
>>> Trivial implementation.
>>>
>>> Signed-off-by: Asahi Lina <lina@asahilina.net>
>>
>> The commit message is a bit short, but the change itself looks fine.
>>
>> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
>
> It's so trivial I just didn't know what else to write... suggestions
> welcome (for this or next time I have a patch like this) ^^
>
> ~ Lina
Adding some sort of motivation usually works quite well, e.g.:
Make it possible to use a CString with the `pr_*` macros directly, that
is, instead of
pr_debug!("trying to open {:?}\n", &*filename);
we can now write
pr_debug!("trying to open {:?}\n", filename);
Alice
next prev parent reply other threads:[~2023-07-14 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 9:19 [PATCH] rust: kernel: str: Implement Debug for CString Asahi Lina
2023-07-14 9:48 ` Alice Ryhl
2023-07-14 12:21 ` Asahi Lina
2023-07-14 13:46 ` Martin Rodriguez Reboredo
2023-07-14 10:05 ` Ariel Miculas
2023-07-14 14:02 ` Alice Ryhl [this message]
2023-07-14 15:01 ` Miguel Ojeda
2023-10-25 16:18 ` Ariel Miculas (amiculas)
2023-10-25 16:55 ` Miguel Ojeda
2023-07-15 10:00 ` Benno Lossin
2023-12-13 18:43 ` 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=20230714140201.383439-1-aliceryhl@google.com \
--to=aliceryhl@google.com \
--cc=alex.gaynor@gmail.com \
--cc=ariel.miculas@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--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