From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: timo.gr@hotmail.de
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH] lib/Kconfig.debug: fix grammar in RUST_BUILD_ASSERT_ALLOW
Date: Fri, 16 Jun 2023 03:17:35 +0200 [thread overview]
Message-ID: <CANiq72kf=VktsDS6ctLxVt70EGtkSwfx+Z2=qNMdyQf81pQ3dA@mail.gmail.com> (raw)
In-Reply-To: <PAXP190MB1631B7C90A99FCEBB1594AAE8B4DA@PAXP190MB1631.EURP190.PROD.OUTLOOK.COM>
On Mon, Jun 5, 2023 at 6:12 PM <timo.gr@hotmail.de> wrote:
>
> From: Timgrau <timo.gr@hotmail.de>
>
> Just a grammar fix in lib/Kconfig.debug, under the config option RUST_BUILD_ASSERT_ALLOW.
>
> Signed-off-by: Timgrau <timo.gr@hotmail.de>
> Suggested-by: Miguel Ojeda <ojeda@kernel.org>
> Link: https://github.com/Rust-for-Linux/linux/issues/1006#issue-1696318406
> Closes: https://github.com/Rust-for-Linux/linux/issues/1006#issue-1696318406
Thanks for the patch!
A few notes:
- From a quick look, I think "Timgrau" is not a known identity to
the kernel, right? (e.g. I couldn't find any other commit on that
name). Assuming I am not mistaken, could you please instead your real
name?
- When I wrote the report, I wrongly suggested `Suggested-by` +
`Link` because I didn't consider this a "bug". But you are probably
right that should be considered a fix anyway, so instead we should use
`Reported-by` and `Closes`. So could you please remove the `Link` and
change the `Suggested` to `Reported`?
- Also, since this is now a fix, could you please also add the `Fixes:` tag?
- For the `Closes`, you can remove the URL fragment part, i.e.
`#issue-1696318406`, since it is anyway the first comment.
If you could change those bits and send a v2, that would be great. Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2023-06-16 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 16:12 [PATCH] lib/Kconfig.debug: fix grammar in RUST_BUILD_ASSERT_ALLOW timo.gr
2023-06-16 1:17 ` Miguel Ojeda [this message]
2023-06-25 10:05 ` Timo Grautstück
2023-08-02 15:29 ` Miguel Ojeda
2024-10-04 8:55 ` [PATCH v2] " Timo Grautstück
2024-10-05 19:13 ` Miguel Ojeda
2024-10-06 14:02 ` [PATCH v3] " Timo Grautstück
2024-10-07 17:14 ` 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='CANiq72kf=VktsDS6ctLxVt70EGtkSwfx+Z2=qNMdyQf81pQ3dA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=timo.gr@hotmail.de \
/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).