From: Andrew Morton <akpm@linux-foundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.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 failure after merge of the mm-hotfixes tree
Date: Mon, 12 Dec 2022 18:23:04 -0800 [thread overview]
Message-ID: <20221212182304.fc148bf08bc17e58ec4b6674@linux-foundation.org> (raw)
In-Reply-To: <e8dfaf60-ff35-66d3-7bc1-f11eaaef642a@huawei.com>
On Tue, 13 Dec 2022 09:34:24 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> Hi, this patch relays on Tony Luck's Patch series "Copy-on-write poison
> recovery".[1]
> and tested ppc64_defconfig based on next-20221208, it's no build failure
I reordered these a couple of days ago, not sure how Stephen got a hold
of this tree - perhaps I wasn't pushy enough.
Stephen, quoting the mm-everything tag would be helpful, but rarely
useful so only if you're feeling bored ;)
> I think it is not very hotfix, also will send v3 to address some comments
> we could adjust the patch order in mm tree, thanks.
This patch is still in mm-unstable so updates won't be a problem.
Soon, please.
next prev parent reply other threads:[~2022-12-13 2:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 22:30 linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2022-12-13 1:34 ` Kefeng Wang
2022-12-13 2:23 ` Andrew Morton [this message]
2022-12-13 2:45 ` Stephen Rothwell
2022-12-13 2:54 ` Kefeng Wang
-- strict thread matches above, loose matches on Subject: below --
2025-12-07 21:35 Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09 1:37 ` Andrew Morton
2025-08-21 6:05 Stephen Rothwell
2025-08-21 9:49 ` Harry Yoo
2025-05-28 23:59 Stephen Rothwell
2025-05-29 0:02 ` Andrew Morton
2025-05-29 1:57 ` Stephen Rothwell
2025-05-29 0:03 ` Stephen Rothwell
2024-07-01 0:16 Stephen Rothwell
2024-07-01 1:01 ` Stephen Rothwell
2024-07-01 18:15 ` Yang Shi
2024-07-02 22:44 ` Stephen Rothwell
2024-07-02 23:22 ` Stephen Rothwell
2024-07-03 0:40 ` Yang Shi
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-11-25 1:10 Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` Stephen Rothwell
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=20221212182304.fc148bf08bc17e58ec4b6674@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wangkefeng.wang@huawei.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