From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: zhuyinbo <zhuyinbo@loongson.cn>, Rob Herring <robh@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
wanghongliang@loongson.cn, Liu Peibao <liupeibao@loongson.cn>,
Mark Brown <broonie@kernel.org>,
Jianmin Lv <lvjianmin@loongson.cn>,
loongson-kernel@lists.loongnix.cn, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: spi: add loongson spi
Date: Wed, 29 Mar 2023 10:05:53 +0200 [thread overview]
Message-ID: <3850df80-d3e9-00a8-df4a-fddd86706373@linaro.org> (raw)
In-Reply-To: <4ed4e0b6-63a8-a5b1-fed9-64a6d036459b@loongson.cn>
On 29/03/2023 03:12, zhuyinbo wrote:
> This patch need depend on
> https://lore.kernel.org/all/20230323025229.2971-1-zhuyinbo@loongson.cn/
> then the spi yaml file will build successful. That changelog had record it.
Thus it cannot be merged now. Do not resend it till dependency hits
mainline (since you decided not to go with Rob's advice).
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-29 8:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 11:22 [PATCH v4 0/2] spi: loongson: add bus driver for the loongson spi Yinbo Zhu
2023-03-28 11:22 ` [PATCH v4 1/2] dt-bindings: spi: add " Yinbo Zhu
2023-03-28 11:30 ` zhuyinbo
2023-03-28 12:57 ` Rob Herring
2023-03-29 1:12 ` zhuyinbo
2023-03-29 8:05 ` Krzysztof Kozlowski [this message]
2023-03-29 10:32 ` zhuyinbo
2023-03-29 10:39 ` zhuyinbo
2023-03-29 11:37 ` Krzysztof Kozlowski
2023-03-30 3:00 ` zhuyinbo
2023-03-29 8:06 ` Krzysztof Kozlowski
2023-03-29 10:30 ` zhuyinbo
2023-03-28 11:22 ` [PATCH v4 2/2] spi: loongson: add bus driver for the loongson spi controller Yinbo Zhu
2023-03-28 11:35 ` [PATCH v4 0/2] spi: loongson: add bus driver for the loongson spi Andi Shyti
2023-03-28 11:53 ` zhuyinbo
2023-03-29 8:07 ` Krzysztof Kozlowski
2023-03-30 3:46 ` zhuyinbo
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=3850df80-d3e9-00a8-df4a-fddd86706373@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=wanghongliang@loongson.cn \
--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 NNTP newsgroup(s).