All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: 1579567540@qq.com, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Elaine Zhang <zhangqing@rock-chips.com>,
	Ulf Hansson <ulfh@kernel.org>,
	Finley Xiao <finley.xiao@rock-chips.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 2/2] pmdomain: rockchip: Add RK3572 boot peripheral domains
Date: Mon, 26 Oct 2026 12:53:59 +0100	[thread overview]
Message-ID: <3329883.fEcJ0Lxnt5@phil> (raw)
In-Reply-To: <d4e92131-ceb8-4143-b8f8-21e7f9638bdb@rock-chips.com>

Hi Finley,

Am Montag, 26. Oktober 2026, 12:37:06 Mitteleuropäische Normalzeit schrieb Finley Xiao:
> 
> 在 2026/10/26 16:47, Finley Xiao 写道:
> >
> > 在 2026/10/26 11:21, Cunhao Lu via B4 Relay 写道:
> >> From: Finley Xiao <finley.xiao@rock-chips.com>
> >>
> >> Add support for the RK3572 NVM0, NVM1, PHP, and VOP power domains.
> >>
> >> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> 
> I have to point out that the changes (the shutdown/restore
> rework, pending-state tracking, etc.) were not made by me, and I have
> not reviewed them in detail. Therefore, I should not remain as the
> author (From:) of this patch, nor should my Signed-off-by be kept on
> it.

As this seemingly comes from the vendor-tree, _some_ Rockchip authorship
should be kept I think?

Do you have a suggestion who that should be other than you? :-)

I guess as you suggested splitting this anyway, that authorship
could also be split.


Thanks
Heiko





WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: 1579567540@qq.com, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Elaine Zhang <zhangqing@rock-chips.com>,
	Ulf Hansson <ulfh@kernel.org>,
	Finley Xiao <finley.xiao@rock-chips.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 2/2] pmdomain: rockchip: Add RK3572 boot peripheral domains
Date: Mon, 26 Oct 2026 12:53:59 +0100	[thread overview]
Message-ID: <3329883.fEcJ0Lxnt5@phil> (raw)
In-Reply-To: <d4e92131-ceb8-4143-b8f8-21e7f9638bdb@rock-chips.com>

Hi Finley,

Am Montag, 26. Oktober 2026, 12:37:06 Mitteleuropäische Normalzeit schrieb Finley Xiao:
> 
> 在 2026/10/26 16:47, Finley Xiao 写道:
> >
> > 在 2026/10/26 11:21, Cunhao Lu via B4 Relay 写道:
> >> From: Finley Xiao <finley.xiao@rock-chips.com>
> >>
> >> Add support for the RK3572 NVM0, NVM1, PHP, and VOP power domains.
> >>
> >> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> 
> I have to point out that the changes (the shutdown/restore
> rework, pending-state tracking, etc.) were not made by me, and I have
> not reviewed them in detail. Therefore, I should not remain as the
> author (From:) of this patch, nor should my Signed-off-by be kept on
> it.

As this seemingly comes from the vendor-tree, _some_ Rockchip authorship
should be kept I think?

Do you have a suggestion who that should be other than you? :-)

I guess as you suggested splitting this anyway, that authorship
could also be split.


Thanks
Heiko





_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-10-26 11:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  3:21 [PATCH v3 0/2] pmdomain: rockchip: Add RK3572 boot peripheral domains Cunhao Lu
2026-10-26  3:21 ` Cunhao Lu via B4 Relay
2026-10-26  3:21 ` Cunhao Lu via B4 Relay
2026-10-26  3:21 ` [PATCH v3 1/2] dt-bindings: power: rockchip: Add RK3572 power domains Cunhao Lu
2026-10-26  3:21   ` Cunhao Lu via B4 Relay
2026-10-26  3:21   ` Cunhao Lu via B4 Relay
2026-10-27 10:16   ` Krzysztof Kozlowski
2026-10-27 10:16     ` Krzysztof Kozlowski
2026-10-27 10:51     ` Cunhao Lu
2026-10-27 10:51       ` Cunhao Lu
2026-10-26  3:21 ` [PATCH v3 2/2] pmdomain: rockchip: Add RK3572 boot peripheral domains Cunhao Lu
2026-10-26  3:21   ` Cunhao Lu via B4 Relay
2026-10-26  3:21   ` Cunhao Lu via B4 Relay
2026-10-26  7:17   ` sashiko-bot
2026-10-26  7:51     ` Cunhao Lu
2026-10-26  8:47   ` Finley Xiao
2026-10-26  8:47     ` Finley Xiao
2026-10-26 11:37     ` Finley Xiao
2026-10-26 11:37       ` Finley Xiao
2026-10-26 11:53       ` Heiko Stuebner [this message]
2026-10-26 11:53         ` Heiko Stuebner
2026-10-27  1:10         ` Finley Xiao
2026-10-27  1:10           ` Finley Xiao
2026-10-27 13:31           ` Heiko Stübner
2026-10-27 13:31             ` Heiko Stübner

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=3329883.fEcJ0Lxnt5@phil \
    --to=heiko@sntech.de \
    --cc=1579567540@qq.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=finley.xiao@rock-chips.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=ulfh@kernel.org \
    --cc=zhangqing@rock-chips.com \
    /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.