Re: linux-next: manual merge of the akpm-current tree with the fscache tree

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

Subject: Re: linux-next: manual merge of the akpm-current tree with the fscache tree
From: David Howells <dhowells@xxxxxxxxxx>
Date: Tue, 02 Mar 2021 16:59:18 +0000
Cc: dhowells@xxxxxxxxxx, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, "Matthew Wilcox (Oracle)" <willy@xxxxxxxxxxxxx>
In-reply-to: <20210301092938.33116d24@canb.auug.org.au>
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
References: <20210301092938.33116d24@canb.auug.org.au> <20210211212437.6d3df60f@canb.auug.org.au>

Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:

> This is now a conflict between the fscache tree and Linus' tree.

I've rebased to -rc1 and repushed.

David

References:
- Re: linux-next: manual merge of the akpm-current tree with the fscache tree
  - From: Stephen Rothwell
- linux-next: manual merge of the akpm-current tree with the fscache tree
  - From: Stephen Rothwell

Prev by Date: next/master baseline: 489 runs, 9 regressions (next-20210302)
Next by Date: linux-next: build warning after merge of the fscache tree
Previous by thread: Re: linux-next: manual merge of the akpm-current tree with the fscache tree
Next by thread: linux-next: manual merge of the akpm-current tree with the fscache tree
Index(es):
- Date
- Thread

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

Powered by Linux