All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Roman Gushchin <roman.gushchin@linux.dev>,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>
Subject: Re: Sashiko review feedback (was Re: [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver)
Date: Tue, 31 Mar 2026 09:18:07 +0200	[thread overview]
Message-ID: <act1L-2tQV4fHyU7@shikoro> (raw)
In-Reply-To: <20260330135050.GD22278@macsyma.local>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hi Ted,

> I was thinking about proposing some tagging convention such as:
> 
>    Suggested-by: Sashiko:Gemini 3.1 Pro
> or
>    Reviewed-by: Sashiko:Gemini 3.1 Pro
> 
> to Documentation/process/coding-assistants.rst.  Alas, neither is
> perfect.

Yes, maybe an email is not so much needed and the information about
Sashiko and Gemini is much more relevant.

> Suggested-by: is generlly used when someone inspires a particular
> commit.  This might apply if Sashiko found a problem as an incidental
> finding, which we then fixed in a subsequent commit.  An example of
> this might be[1], or in the case which you suggested above.  But what

What about Reported-by? The required closes by would then link to the
actual report:

Reported-by: Sashiko:Gemini 3.1 Pro
Closes: https://sashiko.dev/#/patchset/20260319105947.6237-1-wsa%2Brenesas%40sang-engineering.com

The drawback currently is that only the whole report for the patchset
can be linked. But probably Sashiko-reports could have some more HTML
tags to reference only the paragraph needed.

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-03-31  7:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 13:06 [PATCH 0/3] soc: renesas: add MFIS driver Wolfram Sang
2026-03-17 13:06 ` [PATCH 1/3] dt-bindings: soc: renesas: add MFIS binding documentation Wolfram Sang
2026-03-18  9:17   ` Krzysztof Kozlowski
2026-03-18  9:19     ` Krzysztof Kozlowski
2026-03-19  8:54     ` Geert Uytterhoeven
2026-03-19  8:58       ` Krzysztof Kozlowski
2026-03-31  7:10         ` Wolfram Sang
2026-03-31  7:14           ` Krzysztof Kozlowski
2026-03-31  7:40             ` Wolfram Sang
2026-03-31  7:52               ` Krzysztof Kozlowski
2026-03-31  7:18           ` Krzysztof Kozlowski
2026-03-31  7:33             ` Wolfram Sang
2026-03-19  9:15     ` Wolfram Sang
2026-03-18  9:17   ` Krzysztof Kozlowski
2026-03-19  8:58   ` Geert Uytterhoeven
2026-03-17 13:06 ` [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver Wolfram Sang
2026-03-19 12:58   ` Geert Uytterhoeven
2026-03-22 19:58     ` Wolfram Sang
2026-03-23  8:12       ` Geert Uytterhoeven
2026-03-23  9:29         ` Wolfram Sang
2026-03-23 10:06           ` Geert Uytterhoeven
2026-03-22  8:59   ` Sashiko review feedback (was Re: [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver) Wolfram Sang
2026-03-23 10:02     ` Geert Uytterhoeven
2026-03-23 10:58       ` Wolfram Sang
2026-03-24  2:21     ` Roman Gushchin
2026-03-24  6:18       ` Wolfram Sang
2026-03-24 14:54         ` Roman Gushchin
2026-03-30  8:57           ` Wolfram Sang
2026-03-30 13:50             ` Theodore Tso
2026-03-31  7:18               ` Wolfram Sang [this message]
2026-03-31  7:44                 ` Geert Uytterhoeven
2026-03-31  7:53                   ` Wolfram Sang
2026-03-29 17:05   ` [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver Jassi Brar
2026-03-31  9:03     ` Wolfram Sang
2026-03-17 13:06 ` [PATCH 3/3] soc: renesas: add X5H PRR support Wolfram Sang
2026-03-19  9:04   ` Geert Uytterhoeven

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=act1L-2tQV4fHyU7@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=geert+renesas@glider.be \
    --cc=jassisinghbrar@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=roman.gushchin@linux.dev \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.