From: wjjsn <wjjsn@qq.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, robh <robh@kernel.org>,
krzk+dt <krzk+dt@kernel.org>, conor+dt <conor+dt@kernel.org>,
chenhuacai <chenhuacai@kernel.org>,
zhuyinbo <zhuyinbo@loongson.cn>,
mturquette <mturquette@baylibre.com>, sboyd <sboyd@kernel.org>
Cc: linux-clk <linux-clk@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
loongarch <loongarch@lists.linux.dev>, kernel <kernel@xen0n.name>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] loongson2 clk: introduce ls2k1000 specific compatible
Date: Tue, 24 Mar 2026 23:40:45 +0800 [thread overview]
Message-ID: <tencent_8862A8A2CC025DA4A7364DE3BC36A685000A@qq.com> (raw)
In-Reply-To: <1d8def7c-bc9d-46c0-8584-67848bf12ef4@kernel.org>
On 3/23/26 04:30, Krzysztof Kozlowski wrote:
> On 22/03/2026 16:27, wjjsn@qq.com wrote:
>> Please ignore this series. I mistakenly labeled it as v2 (again). I have just sent out v3 which supersedes this one. Sorry for the noise.
>>
>>
>
> Can you slow down and read the feedback you received?
>
> Best regards,
> Krzysztof
I just saw the mail now.
I'm really, really sorry.
I don't know why all the emails you sent me
were classified as spam.
Next, I will carefully review the feedback
you provided and make thorough revisions.
I'm really, really sorry
Best Regards,
wjjsn
next prev parent reply other threads:[~2026-03-24 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 15:08 [PATCH v2 0/2] loongson2 clk: introduce ls2k1000 specific compatible wjjsn
[not found] ` <tencent_78A85ECCF65F70A7A24D63BF52A6BD03320A@qq.com>
2026-03-22 20:30 ` Krzysztof Kozlowski
2026-03-24 15:40 ` wjjsn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-22 8:19 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=tencent_8862A8A2CC025DA4A7364DE3BC36A685000A@qq.com \
--to=wjjsn@qq.com \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).