From: Yinbo Zhu <zhuyinbo@loongson.cn>
To: Arnd Bergmann <arnd@arndb.de>, patchwork-bot+linux-soc@kernel.org
Cc: soc@kernel.org, zhuyinbo@loongson.cn
Subject: Re: [PATCH v7 1/2] soc: loongson: add GUTS driver for loongson-2 platforms
Date: Tue, 15 Nov 2022 10:59:30 +0800 [thread overview]
Message-ID: <2cfeb906-4d5d-5049-574f-40787728845a@loongson.cn> (raw)
In-Reply-To: <79ecabde-e561-4f7d-8c6f-78331c880e04@app.fastmail.com>
在 2022/11/14 下午11:37, Arnd Bergmann 写道:
> On Mon, Nov 14, 2022, at 16:30, patchwork-bot+linux-soc@kernel.org wrote:
>>
>> Here is the summary with links:
>> - [v7,1/2] soc: loongson: add GUTS driver for loongson-2 platforms
>> (no matching commit)
>> - [v7,2/2] dt-bindings: soc: add loongson-2 chipid
>> https://git.kernel.org/soc/soc/c/06ebd23a33ec
>
> The first commit had a small merge conflict against linux-6.1-rc2
> that I resolved. It's all merged now, but it caused me a little
> extra work, and it means that the automated tracking does not
> work.
I misunderstood your meaning. I mistakenly thought that there was a
problem with the patch test, in fact, it means that the automated
tracking does not work, and I only need supply a no merge confilict
patch and that automated tracking issue will can fix, right?
>
> I suspect the patch was not generated against a recent -rc release
> but either a previous kernel or the current git HEAD commit for
> the loongarch tree.
>
> Arnd
>
prev parent reply other threads:[~2022-11-15 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 5:42 [PATCH v7 1/2] soc: loongson: add GUTS driver for loongson-2 platforms Yinbo Zhu
2022-11-11 5:42 ` [PATCH v7 2/2] dt-bindings: soc: add loongson-2 chipid Yinbo Zhu
2022-11-14 15:30 ` [PATCH v7 1/2] soc: loongson: add GUTS driver for loongson-2 platforms patchwork-bot+linux-soc
2022-11-14 15:37 ` Arnd Bergmann
2022-11-15 1:11 ` Yinbo Zhu
2022-11-15 1:16 ` Yinbo Zhu
2022-11-15 2:59 ` Yinbo Zhu [this message]
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=2cfeb906-4d5d-5049-574f-40787728845a@loongson.cn \
--to=zhuyinbo@loongson.cn \
--cc=arnd@arndb.de \
--cc=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.