From: Timur Tabi <timur@codeaurora.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Shanker Donthineni <shankerd@codeaurora.org>,
awallis@codeaurora.org, Abhimanyu Kapur <abhimany@codeaurora.org>,
Will Deacon <will.deacon@arm.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Vipul Gandhi <vgandhi@codeaurora.org>
Subject: Re: [PATCH 1/3] hvc_dcc: bind driver to core0 for reads and writes
Date: Fri, 26 Jun 2015 14:28:38 -0500 [thread overview]
Message-ID: <CAOZdJXVHjhJLrxO6HCjHXLEJqxXum33B6RyRUZ5KBOu23setnA@mail.gmail.com> (raw)
In-Reply-To: <1435344756-20901-1-git-send-email-timur@codeaurora.org>
On Fri, Jun 26, 2015 at 1:52 PM, Timur Tabi <timur@codeaurora.org> wrote:
>
> Selecting this option will enable code that serializes all console
> input and output to core 0. The DCC driver will create input and
> output FIFOs that all cores will use. Reads and writes from/to DCC
> are handled by a workqueue that runs only core 0.
>
> Signed-off-by: Shanker Donthineni <shankerd@codeaurora.org>
Somehow the original author got dropped when I made this patch. This
patch should say:
From: Shanker Donthineni <shankerd@codeaurora.org>
--
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-06-26 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 18:52 [PATCH 1/3] hvc_dcc: bind driver to core0 for reads and writes Timur Tabi
2015-06-26 18:52 ` [PATCH 2/3] hvc_dcc: don't ignore errors during initialization Timur Tabi
2015-06-26 18:52 ` [PATCH 3/3] [v2] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc Timur Tabi
2015-06-26 19:28 ` Timur Tabi [this message]
2015-06-30 13:58 ` [PATCH 1/3] hvc_dcc: bind driver to core0 for reads and writes Will Deacon
2015-06-30 14:07 ` 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=CAOZdJXVHjhJLrxO6HCjHXLEJqxXum33B6RyRUZ5KBOu23setnA@mail.gmail.com \
--to=timur@codeaurora.org \
--cc=abhimany@codeaurora.org \
--cc=awallis@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=vgandhi@codeaurora.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).