From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] tty: pl011: Work around QDF2400 E44 for earlycon
Date: Tue, 14 Feb 2017 18:48:20 -0500 [thread overview]
Message-ID: <cb5e44c7-3be2-3b10-d133-aaea72c2a485@codeaurora.org> (raw)
In-Reply-To: <0262b9d0-1fd1-ff56-a7c5-b9ab9dcea9a8@codeaurora.org>
On 02/07/2017 11:31 PM, Shanker Donthineni wrote:
> Hi Cov,
>
> The same PL011 driver will be used in virtutal machine, make sure
> your changes have no side effects in VM.
Fundamentally, this is the same workaround as has been tested in the qserver
downstream kernel for over a year.
Cheers,
Cov
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code
Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-02-14 23:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 0:57 [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Christopher Covington
2017-02-08 0:57 ` [PATCH 2/2] tty: pl011: Work around QDF2400 E44 for earlycon Christopher Covington
2017-02-08 4:07 ` Timur Tabi
2017-02-08 4:31 ` Shanker Donthineni
2017-02-14 23:48 ` Christopher Covington [this message]
2017-02-08 4:05 ` [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Timur Tabi
2017-02-08 22:22 ` Christopher Covington
2017-02-08 23:04 ` Timur Tabi
2017-02-14 23:43 ` Christopher Covington
2017-02-08 12:26 ` Robin Murphy
2017-02-08 13:27 ` Timur Tabi
2017-02-08 13:33 ` Mark Rutland
2017-02-08 14:09 ` Timur Tabi
2017-02-08 15:35 ` Marc Zyngier
2017-02-08 16:07 ` Timur Tabi
2017-02-08 21:57 ` Christopher Covington
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=cb5e44c7-3be2-3b10-d133-aaea72c2a485@codeaurora.org \
--to=cov@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).