From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.bootlin.com ([62.4.15.54]) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1fV0Or-0000nY-AQ for linux-mtd@lists.infradead.org; Mon, 18 Jun 2018 20:05:19 +0000 Date: Mon, 18 Jun 2018 22:04:55 +0200 From: Boris Brezillon To: Robert Jarzmik Cc: Mark Brown , Daniel Mack , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, alsa-devel@alsa-project.org Subject: Re: [PATCH v3 00/14] ARM: pxa: switch to DMA slave maps Message-ID: <20180618220455.1810f2a5@bbrezillon> In-Reply-To: <87d0wnrhqz.fsf@belgarion.home> References: <20180617170217.24177-1-robert.jarzmik@free.fr> <20180618104159.24b9fffb@bbrezillon> <87d0wnrhqz.fsf@belgarion.home> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 18 Jun 2018 21:56:20 +0200 Robert Jarzmik wrote: > Boris Brezillon writes: > > > Hi Robert, > > > > On Sun, 17 Jun 2018 19:02:03 +0200 > > Robert Jarzmik wrote: > > > >> As I gathered almost all the required acks, this is an information only post > >> before queuing to the PXA tree. > > > > We'll need an immutable branch/tag containing those changes, just in > > case other conflicting changes get submitted to the NAND driver. > Sure, this branch will be usable from next Wednesday onward, here : > - git fetch https://github.com/rjarzmik/linux.git > tags/pxa-for-4.19-dma_slave_map > > I must insist on "Wednesday", as I need to have one last pass from 0-day kernel > checker to be fully covered, and I'd like as well to know which tree the ASoC > patch will take, ie. if Mark commits to take it, or rather wants to pull from > the imutable branch. > > Until Wednesday, even if the branch exist, consider it doesn't please, and > Thursday morning you can pull if you wish. Don't worry, we're not planning to merge it unless it happens to be required (Stephen Rothwell reporting a merge conflict in next), and we don't have conflicting changes in the pipeline so far.