From: "Heiko Stübner" <heiko@sntech.de>
To: Piotr Zalewski <pZ010001011111@proton.me>,
Diederik de Haas <didi.debian@cknow.org>
Cc: hjc@rock-chips.com, andy.yan@rock-chips.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rockchip/drm: vop2: make vp registers nonvolatile
Date: Sun, 06 Jul 2025 12:46:25 +0200 [thread overview]
Message-ID: <4207630.fIoEIV5pvu@diego> (raw)
In-Reply-To: <DB4WNMVBIWYS.273Z54K6O7DTM@cknow.org>
Am Sonntag, 6. Juli 2025, 12:37:40 Mitteleuropäische Sommerzeit schrieb Diederik de Haas:
> Hi Piotr,
>
> On Sun Jul 6, 2025 at 12:20 PM CEST, Piotr Zalewski wrote:
> >> With a new version of a patch, you're supposed to add the tags you
> >> received for previous versions, like my Tested-by tag [1].
> >>
> >> (unless the new version has changed so much you feel they should not be
> >> carried over; you then need to explicitly describe that and why you
> >> dropped them)
> >
> > Forgot... Should i send it as PATCH v2 RESEND?
>
> I don't think that's needed; the maintainer will let you know if that's
> desirable or that they will add it (back) when committing.
The problem is then remembering to manually collect the tags from a
previous series.
For my reference, it was
Tested-by: Diederik de Haas <didi.debian@cknow.org>
So hopefully I'll remember now :-) and there is no need for a resend
at this time.
Heiko
next prev parent reply other threads:[~2025-07-06 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 8:36 [PATCH v2] rockchip/drm: vop2: make vp registers nonvolatile Piotr Zalewski
2025-07-06 10:07 ` Diederik de Haas
2025-07-06 10:20 ` Piotr Zalewski
2025-07-06 10:37 ` Diederik de Haas
2025-07-06 10:46 ` Heiko Stübner [this message]
2025-08-12 13:23 ` Diederik de Haas
2025-08-14 9:46 ` Heiko Stuebner
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=4207630.fIoEIV5pvu@diego \
--to=heiko@sntech.de \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=didi.debian@cknow.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pZ010001011111@proton.me \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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