[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1fdfa18ae40175ad2fec1f1b6d8b0c9e2ecd1350.camel@intel.com>
Date: Tue, 15 Aug 2023 15:54:12 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
CC: "aneesh.kumar@...ux.ibm.com" <aneesh.kumar@...ux.ibm.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the tip tree
On Tue, 2023-08-15 at 15:29 +1000, Stephen Rothwell wrote:
> Caused by commit
>
> 161e393c0f63 ("mm: Make pte_mkwrite() take a VMA")
>
> interacting with commit
>
> 6440c7b067ef ("powerpc/book3s64/mm: enable transparent pud
> hugepage")
>
> from the mm-stable tree.
>
> I have applied the following patch for today (hopefully it makes
> sense):
Thanks. Seems reasonable to me.
Powered by blists - more mailing lists