From: zhuyinbo <zhuyinbo@loongson.cn>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Jianmin Lv <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, Liu Peibao <liupeibao@loongson.cn>,
loongson-kernel@lists.loongnix.cn, zhuyinbo@loongson.cn
Subject: Re: [PATCH v11 0/2] spi: loongson: add bus driver for the loongson spi
Date: Tue, 23 May 2023 10:08:25 +0800 [thread overview]
Message-ID: <5bbc1f55-1e1c-8c74-f9df-2ec950091ba4@loongson.cn> (raw)
In-Reply-To: <9f6672a2-4a39-4a34-9c2a-0257b05c9699@sirena.org.uk>
在 2023/5/22 下午9:10, Mark Brown 写道:
> On Mon, May 22, 2023 at 09:07:47PM +0800, zhuyinbo wrote:
>> 在 2023/5/22 下午7:56, Mark Brown 写道:
>
>>> What's causing problem is that you patched MAINTAINERS in both patches
>>> but also used the wrong subject line for the first patch so I was having
>>> to fix it up by hand every time.
>
>> spi series patch apply failed, then I have a look about your spi ci
>> tree and that what I need to do is just change the title of [1/2] patch
>> like this in next version ? Correcting the title can solve the problem
>> of patch series apply failure in your tree ? actually, I don't reproduce
>> that apply faile issue in your current spi tree and for-next branch.
>
>> spi: add loongson spi bindings
>
> That's a good title. The patches get reordered in the mailbox when I
> rewrite the title prior to applying them.
okay, I got it. thanks! and I noticed my v11 patch already exists in
your ci tree that contain the title change and I whether need send the
v12 that for fix the binding patch title ?
Thanks,
Yinbo
>
next prev parent reply other threads:[~2023-05-23 2:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 7:10 [PATCH v11 0/2] spi: loongson: add bus driver for the loongson spi Yinbo Zhu
2023-05-22 7:10 ` [PATCH v11 1/2] dt-bindings: spi: add " Yinbo Zhu
2023-05-24 8:56 ` Conor Dooley
2023-05-24 9:44 ` zhuyinbo
2023-05-24 10:29 ` Conor Dooley
2023-05-25 2:22 ` zhuyinbo
[not found] ` <2196dd29-93ee-00f7-65b4-ede73aa8ba77@linaro.org>
2023-06-01 9:51 ` zhuyinbo
2023-06-01 15:30 ` Krzysztof Kozlowski
2023-06-02 6:46 ` zhuyinbo
[not found] ` <69d355ff-90e1-09d2-d4ff-0d7dedc8addb@linaro.org>
2023-06-01 11:38 ` zhuyinbo
2023-05-22 7:10 ` [PATCH v11 2/2] spi: loongson: add bus driver for the loongson spi controller Yinbo Zhu
2023-05-23 12:54 ` andy.shevchenko
2023-05-24 7:52 ` zhuyinbo
2023-05-24 8:42 ` Andy Shevchenko
2023-05-24 10:19 ` Mark Brown
2023-05-25 3:34 ` zhuyinbo
2023-05-25 9:16 ` Andy Shevchenko
2023-05-25 9:28 ` zhuyinbo
2023-05-22 10:34 ` [PATCH v11 0/2] spi: loongson: add bus driver for the loongson spi Mark Brown
2023-05-22 11:44 ` zhuyinbo
2023-05-22 11:56 ` Mark Brown
2023-05-22 13:07 ` zhuyinbo
2023-05-22 13:10 ` Mark Brown
2023-05-23 2:08 ` zhuyinbo [this message]
2023-05-23 9:57 ` Mark Brown
2023-05-23 11:01 ` zhuyinbo
2023-07-31 19:57 ` Mark Brown
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=5bbc1f55-1e1c-8c74-f9df-2ec950091ba4@loongson.cn \
--to=zhuyinbo@loongson.cn \
--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=wanghongliang@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).