From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Kumar Gala <galak@codeaurora.org>
Cc: Ankit Jindal <ankit.jindal@linaro.org>,
linux-kernel@vger.kernel.org, "Hans J. Koch" <hjk@hansjkoch.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
patches@apm.com, linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Tushar Jagad <tushar.jagad@linaro.org>,
devicetree@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Varka Bhadram <varkabhadram@gmail.com>
Subject: Re: [PATCH v3 2/6] uio: Add new UIO_MEM_PHYS_CACHE type for mem regions
Date: Fri, 31 Oct 2014 09:35:57 +0000 [thread overview]
Message-ID: <20141031093557.GT27405@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <6D33D50E-2DD1-482C-B05E-45B237F3B779@codeaurora.org>
On Tue, Oct 21, 2014 at 08:38:23AM +0200, Kumar Gala wrote:
> Rather than adding a new type, why not allow the driver to set the
Please wrap your message.
That doesn't work. A pgprot_t contains more than just memory type
information. It also contains access permissions. In other words,
if the user requested read-only or a read-write mapping, the
permissions will be different.
If you always use your stored pgprot_t, then you will override the
users requested permissions.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-10-31 9:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 5:56 [PATCH v3 0/6] UIO driver for APM X-Gene QMTM Ankit Jindal
2014-10-21 5:56 ` [PATCH v3 1/6] uio: code style cleanup Ankit Jindal
2014-10-21 5:56 ` [PATCH v3 2/6] uio: Add new UIO_MEM_PHYS_CACHE type for mem regions Ankit Jindal
2014-10-21 6:38 ` Kumar Gala
2014-10-31 9:30 ` Ankit Jindal
2014-10-31 13:39 ` Kumar Gala
[not found] ` <4B098F57-E202-412C-B54D-085A46792EDC-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-11-05 12:55 ` Ankit Jindal
[not found] ` <CAPTm99UUA0Oe40uH73Rj8_hvyMYwuxcKhFvU_KVZxmKpR1jn2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-05 15:09 ` Kumar Gala
2014-11-10 11:53 ` Ankit Jindal
2014-10-31 9:35 ` Russell King - ARM Linux [this message]
2014-10-21 5:56 ` [PATCH v3 3/6] Documentation: Update documentation for UIO_MEM_PHYS_CACHE Ankit Jindal
2014-10-21 5:56 ` [PATCH v3 4/6] uio: Add X-Gene QMTM UIO driver Ankit Jindal
2014-10-21 6:04 ` Varka Bhadram
2014-10-21 6:16 ` Ankit Jindal
2014-10-21 6:17 ` Varka Bhadram
2014-10-21 6:23 ` Ankit Jindal
2014-10-21 5:56 ` [PATCH v3 5/6] Documentation: dt-bindings: Add binding info for " Ankit Jindal
2014-10-21 9:14 ` Mark Rutland
2014-10-21 10:05 ` Arnd Bergmann
2014-10-31 10:04 ` Ankit Jindal
[not found] ` <CAPTm99X9k+cfELMLL8_PmYN6RNn7CL7KugnV5JKcW6Jqhs8idg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-31 10:09 ` Mark Rutland
2014-10-31 10:15 ` Ankit Jindal
2014-10-21 5:56 ` [PATCH v3 6/6] MAINTAINERS: Add entry for APM " Ankit Jindal
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=20141031093557.GT27405@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=ankit.jindal@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patches@apm.com \
--cc=robh+dt@kernel.org \
--cc=tushar.jagad@linaro.org \
--cc=varkabhadram@gmail.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).