public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: wjjsn <wjjsn@qq.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	chenhuacai@kernel.org, zhuyinbo@loongson.cn,
	mturquette@baylibre.com, sboyd@kernel.org
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev, kernel@xen0n.name,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: clock: loongson,ls2k: Add ls2k1000 compatible and deprecate legacy
Date: Sun, 22 Mar 2026 21:28:21 +0100	[thread overview]
Message-ID: <00525f82-b310-4ea6-a60d-46c0b626bb93@kernel.org> (raw)
In-Reply-To: <tencent_98546566F32FCE5313A7355EF1D288011909@qq.com>

On 22/03/2026 16:20, wjjsn wrote:
> Add a SoC-specific compatible string "loongson,ls2k1000-clk" for
> Loongson-2K1000.
> 
> Mark the legacy "loongson,ls2k-clk" compatible as deprecated using
> the structured "deprecated: true" property instead of relying on
> textual description.
> 
> Update the example to use the new compatible.
> 
> Signed-off-by: wjjsn <wjjsn@qq.com>

So you completely ignored the feedback, did not respond to it and again
send multiple versions and duplicates within short timeframe.

Best regards,
Krzysztof

  reply	other threads:[~2026-03-22 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260322152030.60257-1-wjjsn@qq.com>
2026-03-22 15:20 ` [PATCH v3 1/2] dt-bindings: clock: loongson,ls2k: Add ls2k1000 compatible and deprecate legacy wjjsn
2026-03-22 20:28   ` Krzysztof Kozlowski [this message]
2026-03-22 15:20 ` [PATCH v3 2/2] clk: loongson2: Add ls2k1000 compatible wjjsn

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=00525f82-b310-4ea6-a60d-46c0b626bb93@kernel.org \
    --to=krzk@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@xen0n.name \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=wjjsn@qq.com \
    --cc=zhuyinbo@loongson.cn \
    /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