From: Will Deacon <will.deacon@arm.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mark Rutland <Mark.Rutland@arm.com>,
Rob Herring <robh@kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] arm64: updates for 4.3
Date: Thu, 10 Sep 2015 18:02:57 +0100 [thread overview]
Message-ID: <20150910170257.GH22439@arm.com> (raw)
In-Reply-To: <CAOZdJXX_avYXi9JSk=Ge6fuBLzS1n2jd7yBmhnFx4u_ptvNS5A@mail.gmail.com>
On Thu, Sep 10, 2015 at 05:58:43PM +0100, Timur Tabi wrote:
> On Fri, Sep 4, 2015 at 5:26 AM, Will Deacon <will.deacon@arm.com> wrote:
> >
> > * Hide direct DCC access from userspace
>
> Doesn't this make sense only if DCC is enabled for ARM64? These
> patches are not part of your patchset:
>
> [v5] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc
> [v3] hvc_dcc: don't ignore errors during initialization
Those patches should go via the usual route for tty changes (i.e. Greg).
I merged the arm64 change here because it (a) makes sense as a standalone
patch and (b) is a dependency for your other stuff.
Will
next prev parent reply other threads:[~2015-09-10 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 10:26 [GIT PULL] arm64: updates for 4.3 Will Deacon
2015-09-10 16:58 ` Timur Tabi
2015-09-10 17:02 ` Will Deacon [this message]
2015-09-11 21:58 ` Timur Tabi
2015-09-11 22:43 ` Greg Kroah-Hartman
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=20150910170257.GH22439@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.org \
--cc=torvalds@linux-foundation.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