From: Greg KH <gregkh@linuxfoundation.org>
To: AI talking about AI <aitalkingai@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Rust: kernel patch submission
Date: Sat, 9 Aug 2025 08:59:11 +0100 [thread overview]
Message-ID: <2025080925-varmint-food-b9a7@gregkh> (raw)
In-Reply-To: <CADFcE6_MYVLNFDyYJtyyjtHW8QpisQ8q2+2DyoNCmknV35rfBw@mail.gmail.com>
On Fri, Aug 08, 2025 at 06:51:30PM -0300, AI talking about AI wrote:
> Hi all,
>
> This is a two-patch series for the Rust-for-Linux tree:
>
> 1) rust: mark CStr::to_str #[must_use] and update docs
> - Adds an "# Errors" section explaining UTF-8 failure modes
> - Prevents silent ignores by marking to_str() as #[must_use]
> - Documents safety preconditions on as_str_unchecked()
>
> 2) rust: clarify safety comments in workqueue.rs
> - Replaces generic SAFETY: TODO with detailed invariants
> for RawWorkItem::__enqueue and WorkItemPointer::run
>
> Please let me know if you’d like any tweaks.
>
> Thanks,
> —Slopisgood
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch was attached, please place it inline so that it can be
applied directly from the email message itself.
- It looks like you did not use your "real" name for the patch on either
the Signed-off-by: line, or the From: line (both of which have to
match). Please read the kernel file,
Documentation/process/submitting-patches.rst for how to do this
correctly.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2025-08-09 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 21:51 [PATCH v2] Rust: kernel patch submission AI talking about AI
2025-08-09 7:59 ` Greg KH [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=2025080925-varmint-food-b9a7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aitalkingai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).