rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Oliver Mangold" <oliver.mangold@pm.me>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
	 <linux-kernel@vger.kernel.org>, <rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH] Rust: Implement a unique reference type URef supplementing ARef
Date: Fri, 21 Feb 2025 10:33:21 +0100	[thread overview]
Message-ID: <87bjuvfxr2.fsf@kernel.org> (raw)
In-Reply-To: <Z7g60a63M7-zm1-G@mango> (Oliver Mangold's message of "Fri, 21 Feb 2025 08:35:32 +0000")

"Oliver Mangold" <oliver.mangold@pm.me> writes:

> On 250221 0912, Greg KH wrote:
>> Nit, please wrap your changelog text at 72 columns or so, checkpatch
>> should have warned you about this, right?
>
> Sorry, I did checkpatch before adding the description. Learned something new, I guess :)

Thanks for sending this!

I can absolutely recommend b4 for sending your work [1]. It will warn
you if you try to send but did not run checkpatch after your latest change.


Best regards,
Andreas Hindborg


[1] https://b4.docs.kernel.org/en/latest/


  reply	other threads:[~2025-02-21  9:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jeyp4dToznpiAQYWHAABrEBIHVfxaIf7ntexop3d2AXQgnlytw3J8YFkX8E8EFKc1-USf_fVZqKhEmuNGE3O0w==@protonmail.internalid>
2025-02-21  8:04 ` [PATCH] Rust: Implement a unique reference type URef supplementing ARef Oliver Mangold
2025-02-21  8:12   ` Greg KH
2025-02-21  8:35     ` Oliver Mangold
2025-02-21  9:33       ` Andreas Hindborg [this message]
2025-02-28 11:10   ` Andreas Hindborg
2025-02-28 11:25     ` Andreas Hindborg
2025-02-28 11:31     ` Oliver Mangold
2025-02-28 12:16       ` Andreas Hindborg
2025-02-28 13:17     ` Miguel Ojeda
2025-03-04  6:19   ` kernel test robot

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=87bjuvfxr2.fsf@kernel.org \
    --to=a.hindborg@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.mangold@pm.me \
    --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).