mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Nanonej Dev" <dev@nanonej.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>, <nova-gpu@lists.linux.dev>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>
Subject: Re: [PATCH v2] gpu: nova-core: gsp: Move gsp register definition into gsp module
Date: Thu, 11 Jun 2026 10:39:53 +0900	[thread overview]
Message-ID: <DJ5U53UC0NV3.3L6GGS2OJ64Q4@nvidia.com> (raw)
In-Reply-To: <9B2MG9ICH2MOGGwTsi0aCGBlEyEO3p-VTk7iR0wgDgBkAYKEu9GC2mc7eAODT5nilASpnSaPdZZjliM9HcvEY96LscSKHF2iDXDXCESptAA=@nanonej.com>

On Wed Jun 10, 2026 at 11:57 PM JST, Nanonej Dev wrote:
> Oh! Didn't think to add this extra tag since your review, sorry! 
>
> Can we add it now? Should I do a V3 to add it? Or not that much of a big deal this time, but should think about it for the next time? 

Don't worry, you did nothing wrong.

This is just the (rudimentary) process by which we state that we have
processed a patch in some way: just reply with the tags carrying our
name/email that we want to stick to the patch [1]. In this case, I've
reviewed it, so I signaled that by giving my `Reviewed-by`.

Since I hadn't given it by the time you sent this patch, there was no
way for you to add it.

The common practice is to collect the tags you received on vN and carry
them onto vN+1 (unless the patch has significantly changed), but in this
case this wasn't necessary since Danilo applied the patch and added the
tags [2].

All this to say that this was a perfectly normal kernel patch review and
there was nothing more for you to do.

[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
[2] https://gitlab.freedesktop.org/drm/rust/kernel/-/commit/3e4bac7b8ca7688fb3aa9c0bf005a5a4256ad578

>
> Anyway let me know and thanks for the feedback!
>
> Also, I check for Proton Mail, as I understand they don't support `format=flowed` so except using there "uservoice" service to ask them to implement  it, I had probably nothing else to do. But I found a git-protonmail service dedicated to use proton mail with git send-email, so maybe it will work? I have to try as I don't know the email protocol well enough to understand on which layer the patch get mangled and if this tool can proxy around the Proton implementation.

Normally `git send-email` or `b4` should do the right thing, but after a
quick search there seems to be recurring server-side mangling issues
with Protonmail, so you might need to use another service to send
patches. B4's web endpoint might be an option [3].

[3] https://b4.docs.kernel.org/en/latest/contributor/send.html

  reply	other threads:[~2026-06-11  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-07 14:10 Antonin Malzieu Ridolfi
2026-06-08 17:36 ` Danilo Krummrich
2026-06-10 13:31 ` Alexandre Courbot
2026-06-10 14:57   ` Nanonej Dev
2026-06-11  1:39     ` Alexandre Courbot [this message]
     [not found]       ` <vvjHdIL6_yt_mjEDbQzZ5naOIbjsntZJ6xoeR495GAgkIFE5m2UJyexmYhPCH9e7Nafptn9rgYNLHZhYPiX4G6l4X75A1MVlg4UzCpjUwLY=@nanonej.com>
2026-06-13 14:21         ` Nanonej Dev
2026-06-10 19:03 ` Danilo Krummrich

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=DJ5U53UC0NV3.3L6GGS2OJ64Q4@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dev@nanonej.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=simona@ffwll.ch \
    /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

all inboxes | Powered by JetHome®