From: Daniel Thompson <daniel.thompson@linaro.org>
To: linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: st-asc: Fix SysRq char handling
Date: Fri, 28 Mar 2014 10:54:51 +0000 [thread overview]
Message-ID: <533554FB.9010506@linaro.org> (raw)
In-Reply-To: <1396003872-30188-1-git-send-email-daniel.thompson@linaro.org>
On 28/03/14 10:51, Daniel Thompson wrote:
> This driver, like several others, uses the upper bits of the character
> to track both real and dummy state. Unfortunately it neglects to mask
> these bits properly when passing the character data around. This means
> neither break detection nor sysrq character handling work correctly.
Many apologies but I have posted this patch twice (the first send had a
grossly incomplete Cc: list).
Please ignore the this thread and use the other one.
Daniel.
next prev parent reply other threads:[~2014-03-28 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 10:51 [PATCH] serial: st-asc: Fix SysRq char handling Daniel Thompson
2014-03-28 10:54 ` Daniel Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-28 10:53 Daniel Thompson
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=533554FB.9010506@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=linux-serial@vger.kernel.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).