From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Mark Brown <broonie@kernel.org>, Daniel Mack <daniel@zonque.org>,
Boris Brezillon <boris.brezillon@bootlin.com>
Cc: 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
Date: Mon, 18 Jun 2018 21:56:20 +0200 [thread overview]
Message-ID: <87d0wnrhqz.fsf@belgarion.home> (raw)
In-Reply-To: <20180618104159.24b9fffb@bbrezillon> (Boris Brezillon's message of "Mon, 18 Jun 2018 10:41:59 +0200")
Boris Brezillon <boris.brezillon@bootlin.com> writes:
> Hi Robert,
>
> On Sun, 17 Jun 2018 19:02:03 +0200
> Robert Jarzmik <robert.jarzmik@free.fr> 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.
Cheers.
--
Robert
next prev parent reply other threads:[~2018-06-18 19:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 17:02 [PATCH v3 00/14] ARM: pxa: switch to DMA slave maps Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 01/14] dmaengine: pxa: use a dma slave map Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 02/14] ARM: pxa: add " Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 03/14] dmaengine: pxa: add a default requestor policy Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 04/14] mmc: pxamci: remove the dmaengine compat need Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 05/14] media: pxa_camera: " Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 06/14] mtd: rawnand: marvell: " Robert Jarzmik
2018-06-17 18:12 ` Daniel Mack
2018-06-18 19:31 ` Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 07/14] net: smc911x: " Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 08/14] net: smc91x: " Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 09/14] ASoC: pxa: " Robert Jarzmik
2018-06-17 18:17 ` Daniel Mack
2018-06-21 8:50 ` Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 10/14] ata: pata_pxa: " Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 11/14] dmaengine: pxa: document pxad_param Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 12/14] dmaengine: pxa: make the filter function internal Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 13/14] ARM: pxa: remove the DMA IO resources Robert Jarzmik
2018-06-17 17:02 ` [PATCH v3 14/14] ARM: pxa: change SSP DMA channels allocation Robert Jarzmik
2018-06-18 8:41 ` [PATCH v3 00/14] ARM: pxa: switch to DMA slave maps Boris Brezillon
2018-06-18 19:56 ` Robert Jarzmik [this message]
2018-06-18 20:04 ` Boris Brezillon
2018-06-20 17:07 ` Robert Jarzmik
2018-06-25 13:07 ` Mark Brown
2018-06-27 15:11 ` Robert Jarzmik
2018-06-27 21:03 ` Daniel Mack
2018-06-28 11:52 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0wnrhqz.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=alsa-devel@alsa-project.org \
--cc=boris.brezillon@bootlin.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).