Netdev List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>, "Cunhao Lu" <1579567540@qq.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Brian Masney <bmasney+clk@redhat.com>,
	Jerome Brunet <jbrunet+clk@baylibre.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Elaine Zhang <zhangqing@rock-chips.com>,
	Richard Cochran <richardcochran@gmail.com>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: clock: rockchip: Add RK3572 CRU
Date: Tue, 27 Oct 2026 12:07:12 +0100	[thread overview]
Message-ID: <c1fc1868-5583-420f-b945-2bf934873713@kernel.org> (raw)
In-Reply-To: <3011736.yaVYbkx8dN@diego>

On 27/10/2026 11:43, Heiko Stübner wrote:
> Am Dienstag, 27. Oktober 2026, 11:17:08 Mitteleuropäische Normalzeit schrieb Krzysztof Kozlowski:
> 
> With code originating in the vendor kernel, it is nice to know what changed,
> but I guess there is a tradeoff between brevity and more details.

Honestly I disagree :). Vendor kernel commits and their messages are
irrelevant per se. They are only useful as source of knowledge, but what
was exactly written there does not matter. Quality is dubious, coding
practices are terrible. We want to extract the knowledge, the important
details, but not the exact commit. We do not care what changed from
downstream to upstream, because we know that downstream sucks so much
that we don't even want to touch it.

> 
> I guess this could be shorted to something less verbose, like
> 
> +++++++++++++
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> [adapted to mainline rockchip clock and reset handling (xin24m input,
>   don't introduce CLK_NR_CLKS, etc ]
> Signed-off-by: Cunhao Lu <1579567540@qq.com>
> +++++++++++++

Yes, if this brings anything useful. For example removal of CLK_NR_CLKS
is completely pointless to mention. How does it explain the hardware or
design choices? How does it explain why this driver was written that or
other way?

Just take the authorship of downstream commits and send them as your
own. Both GPL and DCO allow this and if downstream did not bother to
upstream that stuff, they do not deserve credits.


Best regards,
Krzysztof

  parent reply	other threads:[~2026-10-27 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  6:56 [PATCH v3 0/3] clk: rockchip: Add RK3572 clock and reset support Cunhao Lu via B4 Relay
2026-10-26  6:56 ` [PATCH v3 1/3] dt-bindings: clock: rockchip: Add RK3572 CRU Cunhao Lu via B4 Relay
2026-10-27 10:17   ` Krzysztof Kozlowski
2026-10-27 10:43     ` Heiko Stübner
2026-10-27 11:06       ` Cunhao Lu
2026-10-27 11:07       ` Krzysztof Kozlowski [this message]
2026-10-27 12:53         ` Heiko Stübner
2026-10-26  6:56 ` [PATCH v3 2/3] clk: rockchip: Add internal support for 24-bit fractional dividers Cunhao Lu via B4 Relay
2026-10-26  6:56 ` [PATCH v3 3/3] clk: rockchip: Add RK3572 clock and reset support Cunhao Lu via B4 Relay
     [not found]   ` <0d5de6fd-3150-4898-a652-7f5b64dcaf07@rock-chips.com>
2026-10-26 14:56     ` Cunhao Lu
2026-10-26 17:25       ` Heiko Stübner
2026-10-27  0:57       ` 张晴

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=c1fc1868-5583-420f-b945-2bf934873713@kernel.org \
    --to=krzk@kernel.org \
    --cc=1579567540@qq.com \
    --cc=bmasney+clk@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jbrunet+clk@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox