From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-next-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id E8D5FC4332F
	for <linux-next@archiver.kernel.org>; Tue, 13 Dec 2022 02:23:11 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S234127AbiLMCXK (ORCPT <rfc822;linux-next@archiver.kernel.org>);
        Mon, 12 Dec 2022 21:23:10 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42514 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S231964AbiLMCXJ (ORCPT
        <rfc822;linux-next@vger.kernel.org>); Mon, 12 Dec 2022 21:23:09 -0500
Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A52D5FE2;
        Mon, 12 Dec 2022 18:23:08 -0800 (PST)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by ams.source.kernel.org (Postfix) with ESMTPS id 261DAB80E06;
        Tue, 13 Dec 2022 02:23:07 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id B9A6BC433D2;
        Tue, 13 Dec 2022 02:23:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org;
        s=korg; t=1670898185;
        bh=4dd0Jbjx0gjIAljkmA0ZgSH+i9WhUDx2iCgULP7i/E0=;
        h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
        b=X0HDRs3avxe+K/MYbWB6BMM0/LmaRrkAg7glg+raHBuLqz/wqrjVxgQF9Ag0CyoFt
         7Ce2timhwby7O+C9TqZi/wWJ/PwJDm4m5Gox/fUB5AcILVJ/8zYBNQz/nrCzN0FH7g
         LAx2ahqr3StMu4/N8zAvp6um4SHt+i+EF1yBel+c=
Date:   Mon, 12 Dec 2022 18:23:04 -0800
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
Message-Id: <20221212182304.fc148bf08bc17e58ec4b6674@linux-foundation.org>
In-Reply-To: <e8dfaf60-ff35-66d3-7bc1-f11eaaef642a@huawei.com>
References: <20221213093054.5211da74@canb.auug.org.au>
        <e8dfaf60-ff35-66d3-7bc1-f11eaaef642a@huawei.com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
List-ID: <linux-next.vger.kernel.org>
X-Mailing-List: linux-next@vger.kernel.org

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.