From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] dma-mapping: Constify dma_attrs
Date: Tue, 24 May 2016 02:09:38 -0700 [thread overview]
Message-ID: <20160524090938.GA13166@infradead.org> (raw)
In-Reply-To: <1464071290-15948-1-git-send-email-k.kozlowski@samsung.com>
I think this is moving into the wrong direction. The right fix here
is to get of all the dma_attrs boilerplate code and just replace it
with a simple enum dma_flags. This would simplify both the callers
and most importantly the wrappers for the flag-less versions a lot.
next prev parent reply other threads:[~2016-05-24 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 6:28 [PATCH 0/4] dma-mapping: Constify dma_attrs Krzysztof Kozlowski
2016-05-24 6:28 ` [PATCH 1/4] dma-mapping: Constify attrs passed to dma_get_attr Krzysztof Kozlowski
2016-05-24 6:28 ` [PATCH 2/4] ARM: dma-mapping: Constify attrs passed to internal functions Krzysztof Kozlowski
2016-05-24 8:35 ` Russell King - ARM Linux
2016-05-24 6:28 ` [PATCH 3/4] arm64: " Krzysztof Kozlowski
2016-05-24 6:28 ` [RFC 4/4] dma-mapping: Constify dma_attrs Krzysztof Kozlowski
2016-05-24 9:09 ` Christoph Hellwig [this message]
2016-05-25 12:37 ` [PATCH 0/4] " Krzysztof Kozlowski
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=20160524090938.GA13166@infradead.org \
--to=hch@infradead.org \
--cc=linux-arm-kernel@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).