From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yinbo Zhu <zhuyinbo@loongson.cn>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Jianmin Lv <lvjianmin@loongson.cn>, Yun Liu <liuyun@loongson.cn>,
Yang Li <yang.lee@linux.alibaba.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH v8 2/2] dt-bindings: hpet: add loongson-2 hpet
Date: Wed, 9 Nov 2022 10:24:07 +0100 [thread overview]
Message-ID: <a588a90e-a8ab-7b43-a14b-101bb9f590db@linaro.org> (raw)
In-Reply-To: <b0aed9f8-f82e-3d74-4299-4d77445c2170@loongson.cn>
On 09/11/2022 10:19, Yinbo Zhu wrote:
> Hi maintainer,
>
> please help me merge it to upstream.
> in addition, this patch need rely on
> "https://patchwork.kernel.org/project/linux-clk/list/?series=691497"
Why pinging for v8? Didn't you have v9 and v10?
Several of your Loongson patches had many build errors, pointed out by
lkp. Therefore I have doubts that you test these extensively. This might
be the reason why your patches float around...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-09 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 6:53 [PATCH v8 1/2] clocksource: loongson2_hpet: add hpet driver support Yinbo Zhu
2022-11-03 6:53 ` [PATCH v8 2/2] dt-bindings: hpet: add loongson-2 hpet Yinbo Zhu
2022-11-09 9:19 ` Yinbo Zhu
2022-11-09 9:24 ` Krzysztof Kozlowski [this message]
2022-11-09 9:38 ` Yinbo Zhu
2022-11-09 9:41 ` Yinbo Zhu
2022-11-03 7:14 ` [PATCH v8 1/2] clocksource: loongson2_hpet: add hpet driver support Christophe JAILLET
2022-11-09 9:18 ` Yinbo Zhu
2022-11-09 9:40 ` Yinbo Zhu
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=a588a90e-a8ab-7b43-a14b-101bb9f590db@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyun@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=lvjianmin@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=yang.lee@linux.alibaba.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
all inboxes | Powered by JetHome®