Re: linux-next: build failure after merge of the akpm-current tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: linux-next: build failure after merge of the akpm-current tree
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 14 Feb 2022 08:16:20 +0100
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>
In-reply-to: <20220214180040.44f8316a@canb.auug.org.au>
References: <20220214180040.44f8316a@canb.auug.org.au>
User-agent: Mutt/1.5.17 (2007-11-01)

On Mon, Feb 14, 2022 at 06:00:40PM +1100, Stephen Rothwell wrote:
> Presumably caused by commit
> 
>   5ba71dc7727a ("mm: don't include <linux/memremap.h> in <linux/mm.h>")
> 
> I applied the following patch:

Thanks,

the fixup looks good to me.

References:
- linux-next: build failure after merge of the akpm-current tree
  - From: Stephen Rothwell

Prev by Date: Re: linux-next: manual merge of the block tree with the fscrypt tree
Next by Date: Re: linux-next: manual merge of the scsi-mkp tree with Linus' tree
Previous by thread: linux-next: build failure after merge of the akpm-current tree
Next by thread: linux-next: build failure after merge of the akpm-current tree
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Linux USB Development] [Yosemite News] [Linux SCSI]

Powered by Linux