Re: linux-next: manual merge of the akpm-current tree with the generic-ioremap 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 generic-ioremap tree
From: Christoph Hellwig <hch@xxxxxx>
Date: Sat, 21 Dec 2019 09:32:11 +0100
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Nick Desaulniers <ndesaulniers@xxxxxxxxxx>
In-reply-to: <20191218133025.15356802@canb.auug.org.au>
References: <20191218133025.15356802@canb.auug.org.au>
User-agent: Mutt/1.5.17 (2007-11-01)

Andrew,

do you plan to send this to Linus for 5.5 to fix the warning from the
new devm_ioremap_uc addition in this cycle?  If so I can rebase the
ioremap tree one more time.

Follow-Ups:
- Re: linux-next: manual merge of the akpm-current tree with the generic-ioremap tree
  - From: Andrew Morton

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

Prev by Date: Re: linux-next: manual merge of the generic-ioremap tree with the nvdimm-fixes tree
Next by Date: Re: linux-next: manual merge of the driver-core tree with the keys tree
Previous by thread: linux-next: manual merge of the akpm-current tree with the generic-ioremap tree
Next by thread: Re: linux-next: manual merge of the akpm-current tree with the generic-ioremap tree
Index(es):
- Date
- Thread

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

Powered by Linux