From: "liuqi (BA)" <liuqi115@huawei.com>
To: Will Deacon <will@kernel.org>,
Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the arm-perf tree
Date: Mon, 29 Mar 2021 17:06:20 +0800 [thread overview]
Message-ID: <57d692c4-8469-c3d0-4e8a-3f01953ac5e4@huawei.com> (raw)
In-Reply-To: <20210329084751.GA2965@willie-the-truck>
On 2021/3/29 16:47, Will Deacon wrote:
> On Fri, Mar 26, 2021 at 05:07:41PM +0800, Shaokun Zhang wrote:
>> Apologies for the mistake.
>>
>> Will, shall I send a new version v5 to fix this issue or other?
>
> Please send additional patches on top now that these are queued.
>
> Thanks,
>
> Will
>
> .
>
We'll send a new patch to fix these warnings today, apologies for the
mistake again.
Thanks,
Qi
next prev parent reply other threads:[~2021-03-29 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 8:52 linux-next: build warnings after merge of the arm-perf tree Stephen Rothwell
2021-03-26 9:07 ` Shaokun Zhang
2021-03-29 8:47 ` Will Deacon
2021-03-29 9:06 ` liuqi (BA) [this message]
2021-03-29 10:06 ` Will Deacon
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=57d692c4-8469-c3d0-4e8a-3f01953ac5e4@huawei.com \
--to=liuqi115@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.com \
/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).