From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] [v2] hvc_dcc: disable user-space access to DCC
Date: Thu, 20 Aug 2015 10:22:36 -0500 [thread overview]
Message-ID: <55D5F0BC.4010304@codeaurora.org> (raw)
In-Reply-To: <20150820104645.GD19328@arm.com>
On 08/20/2015 05:46 AM, Will Deacon wrote:
>> If the DCC driver loads, then disable user-space access to the DCC so that
>> >we don't have two entities trying to access the DCC at the same time.
> In the interests of making some headway with this, just drop this patch
> and I'll queue the diff below via the arm64 tree.
Yes, that would be great. Thank you.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2015-08-20 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 23:02 [PATCH 1/3] [v3] hvc_dcc: don't ignore errors during initialization Timur Tabi
2015-08-19 23:02 ` [PATCH 2/3] [v5] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc Timur Tabi
2015-08-19 23:02 ` [PATCH 3/3] [v2] hvc_dcc: disable user-space access to DCC Timur Tabi
2015-08-20 10:46 ` Will Deacon
2015-08-20 13:02 ` Catalin Marinas
2015-08-20 15:22 ` Timur Tabi [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-08 0:16 [PATCH 1/3] [v2] hvc_dcc: don't ignore errors during initialization Timur Tabi
2015-08-08 0:16 ` [PATCH 3/3] [v2] hvc_dcc: disable user-space access to DCC Timur Tabi
2015-08-10 9:47 ` Will Deacon
2015-08-17 22:45 ` Timur Tabi
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=55D5F0BC.4010304@codeaurora.org \
--to=timur@codeaurora.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).