From: Jiri Slaby <jirislaby@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jiri Slaby <jslaby@suse.cz>,
gregkh@suse.de, Arnd Bergmann <arnd@arndb.de>,
alan@linux.intel.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org,
"3.0 3.1 3.2" <stable@vger.kernel.org>
Subject: Re: [PATCH] TTY: fix UV serial console regression
Date: Mon, 16 Jan 2012 14:28:11 +0100 [thread overview]
Message-ID: <4F1425EB.6050703@gmail.com> (raw)
In-Reply-To: <20120112234132.0a973cb9@pyramind.ukuu.org.uk>
On 01/13/2012 12:41 AM, Alan Cox wrote:
>> Unless there is some bad race in the code, the hardware seems to
>> be pretty broken. Otherwise pure MSR read should not cause such a
>> bug, or?
>
> UV serial being what actual hardware and system ?
What exact paramteres are you interested in? dmidecode on this machine
says it's an Altix XE310.
thanks,
--
js
prev parent reply other threads:[~2012-01-16 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EDE988B.6010501@suse.cz>
2012-01-12 21:55 ` [PATCH] TTY: fix UV serial console regression Jiri Slaby
2012-01-12 22:00 ` Greg KH
2012-01-12 23:41 ` Alan Cox
2012-01-16 13:28 ` Jiri Slaby [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=4F1425EB.6050703@gmail.com \
--to=jirislaby@gmail.com \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=stable@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).