From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] TTY: hvc_dcc: probe for a JTAG connection before registering
Date: Thu, 17 Oct 2013 15:31:47 -0500 [thread overview]
Message-ID: <52604933.20007@gmail.com> (raw)
In-Reply-To: <20131017202047.GA24568@kroah.com>
On 10/17/2013 03:20 PM, Greg Kroah-Hartman wrote:
> On Thu, Oct 17, 2013 at 02:16:37PM -0500, Rob Herring wrote:
>> On Tue, Sep 24, 2013 at 9:05 PM, Rob Herring <robherring2@gmail.com> wrote:
>>> From: Rob Herring <rob.herring@calxeda.com>
>>>
>>> Enabling the ARM DCC console and using without a JTAG connection will
>>> simply hang the system. Since distros like to turn on all options, this
>>> is a reoccurring problem to debug. We can do better by checking if
>>> anything is attached and handling characters. There is no way to probe
>>> this, so send a newline and check that it is handled.
>>>
>>> Cc: Paolo Pisati <paolo.pisati@canonical.com>
>>> Cc: Tim Gardner <tim.gardner@canonical.com>
>>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> Cc: Jiri Slaby <jslaby@suse.cz>
>>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>>> ---
>>> v2: use time_is_after_jiffies
>>>
>>> drivers/tty/hvc/hvc_dcc.c | 21 +++++++++++++++++++++
>>> 1 file changed, 21 insertions(+)
>>
>> Greg, Jiri,
>>
>> Can you please apply.
>
> I already did, didn't you get an email saying it was applied to my tree?
Ah, yes. Found it buried in my work email. Sorry about that.
Rob
prev parent reply other threads:[~2013-10-17 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 20:30 [PATCH] TTY: hvc_dcc: probe for a JTAG connection before registering Rob Herring
2013-09-23 21:10 ` Tim Gardner
2013-09-23 21:35 ` Rob Herring
2013-09-25 2:05 ` [PATCH v2] " Rob Herring
2013-10-17 19:16 ` Rob Herring
2013-10-17 20:20 ` Greg Kroah-Hartman
2013-10-17 20:31 ` Rob Herring [this message]
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=52604933.20007@gmail.com \
--to=robherring2@gmail.com \
--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).