From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vitaly Kuzmichev <vitaly_kuzmichev@mentor.com>
Cc: <gregkh@linuxfoundation.org>, <hch@lst.de>,
<m.szyprowski@samsung.com>, <robin.murphy@arm.com>,
<linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Additions to default DMA coherent pool
Date: Fri, 7 Jul 2017 23:55:39 +1000 [thread overview]
Message-ID: <20170707235539.073718ed@canb.auug.org.au> (raw)
In-Reply-To: <1499433759-16397-1-git-send-email-vitaly_kuzmichev@mentor.com>
Hi Vitaly,
On Fri, 7 Jul 2017 16:22:39 +0300 Vitaly Kuzmichev <vitaly_kuzmichev@mentor.com> wrote:
>
> v2:
> Since linux-next now includes Vladimir Murzin's version of default DMA
> coherent pool [1] our version is not required now and even causes merge
> conflict. The difference between two versions is not really significant
> except one serious problem with CONFIG_DMA_CMA. Please see patch v2 1/2
> for details.
> So that I have rebased our work on linux-next/master branch, and sending
> this patchset with necessary additions for default DMA pool feature.
>
> Patch v2 2/2 adds 'dmainfo' to ProcFS to show available DMA regions.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=93228b44c33a572cb36cec2dbed42e9bdbc88d79
This is now also in Linus' tree. You should rebase your work on that
commit (or just Linus' tree), not linux-next.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-07-07 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 14:51 [PATCH 0/2] Implement default DMA coherent pool vitaly_kuzmichev
2017-07-03 14:51 ` [PATCH 1/2] drivers: dma-coherent: Add support for " vitaly_kuzmichev
2017-07-04 21:02 ` kbuild test robot
2017-07-05 5:55 ` kbuild test robot
2017-07-10 0:36 ` Rob Herring
2017-07-03 14:51 ` [PATCH 2/2] drivers: dma-coherent: show per-device DMA region utilization via procfs vitaly_kuzmichev
2017-07-07 13:22 ` [PATCH v2 0/2] Additions to default DMA coherent pool Vitaly Kuzmichev
2017-07-07 13:22 ` [PATCH v2 1/2] drivers: dma-coherent: Fix dev->cma_area vs dev->dma_mem breakage Vitaly Kuzmichev
2017-07-07 14:27 ` Christoph Hellwig
2017-07-07 15:40 ` Vladimir Murzin
2017-07-07 16:06 ` Robin Murphy
2017-07-07 16:44 ` Vladimir Murzin
2017-07-07 17:55 ` Robin Murphy
2017-07-10 13:42 ` Vladimir Murzin
2017-07-11 14:19 ` Christoph Hellwig
2017-07-07 13:23 ` [PATCH v2 2/2] drivers: dma-coherent: show per-device DMA region utilization via procfs Vitaly Kuzmichev
2017-07-07 14:28 ` Christoph Hellwig
2017-07-07 13:55 ` Stephen Rothwell [this message]
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=20170707235539.073718ed@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=vitaly_kuzmichev@mentor.com \
/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).