From: Andrew Morton <akpm@linux-foundation.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: linux@arm.linux.org.uk, mchehab@osg.samsung.com,
robin.murphy@arm.com, tfiga@chromium.org,
m.szyprowski@samsung.com, pawel@osciak.com,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
hch@infradead.org, k.debski@samsung.com,
laurent.pinchart+renesas@ideasonboard.com, corbet@lwn.net,
mike.looijmans@topic.nl, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, will.deacon@arm.com,
jtp.park@samsung.com, penguin-kernel@i-love.sakura.ne.jp,
kyungmin.park@samsung.com, carlo@caione.org,
linux-media@vger.kernel.org, dan.j.williams@intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/5] dma-mapping: Patches for speeding up allocation
Date: Tue, 26 Jan 2016 15:59:37 -0800 [thread overview]
Message-ID: <20160126155937.6a4e4165d1cf4e513d62e942@linux-foundation.org> (raw)
In-Reply-To: <1452533428-12762-1-git-send-email-dianders@chromium.org>
On Mon, 11 Jan 2016 09:30:22 -0800 Douglas Anderson <dianders@chromium.org> wrote:
> This series of patches will speed up memory allocation in dma-mapping
> quite a bit.
This is pretty much all ARM and driver stuff so I think I'll duck it.
But I can merge it if nobody else feels a need to.
I saw a few acked-by/tested-by/etc from the v5 posting which weren't
carried over into v6 (might have been a timing race), so please fix
that up if there's an opportunity.
Regarding the new DMA_ATTR_ALLOC_SINGLE_PAGES hint: I suggest adding
"DMA_ATTR_ALLOC_SINGLE_PAGES is presently implemented only on ARM" to
the docs. Or perhaps have a shot at implementing it elsewhere.
Typo in 4/5 changelog: "reqiurements"
next prev parent reply other threads:[~2016-01-26 23:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 17:30 [PATCH v6 0/5] dma-mapping: Patches for speeding up allocation Douglas Anderson
2016-01-11 17:30 ` [PATCH v6 4/5] videobuf2-dc: Let drivers specify DMA attrs Douglas Anderson
2016-02-01 11:40 ` Mauro Carvalho Chehab
2016-02-01 13:29 ` Marek Szyprowski
2016-02-01 21:37 ` Doug Anderson
2016-02-17 17:00 ` Hans Verkuil
2016-02-17 17:26 ` Doug Anderson
2016-02-18 5:58 ` Tomasz Figa
2016-01-11 17:30 ` [PATCH v6 5/5] s5p-mfc: Set DMA_ATTR_ALLOC_SINGLE_PAGES Douglas Anderson
2016-01-26 23:31 ` [PATCH v6 0/5] dma-mapping: Patches for speeding up allocation Javier Martinez Canillas
2016-01-26 23:59 ` Andrew Morton [this message]
2016-01-27 0:39 ` Doug Anderson
2016-01-29 21:52 ` Olof Johansson
2016-01-29 21:58 ` Doug Anderson
2016-01-29 22:14 ` Doug Anderson
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=20160126155937.6a4e4165d1cf4e513d62e942@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=carlo@caione.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hch@infradead.org \
--cc=jtp.park@samsung.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@osg.samsung.com \
--cc=mike.looijmans@topic.nl \
--cc=pawel@osciak.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=robin.murphy@arm.com \
--cc=tfiga@chromium.org \
--cc=will.deacon@arm.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).