From: Stuart Anderson <anderson@netsweng.com>
To: "J. Mayer" <l_indien@magic.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PPC termios structure ordering
Date: Wed, 18 Apr 2007 14:47:55 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704181447220.22280@trantor.stuart.netsweng.com> (raw)
In-Reply-To: <1176921275.6333.72.camel@rapid>
On Wed, 18 Apr 2007, J. Mayer wrote:
>> With this change, both host and target 'stty -a' give the same output.
>
> Thanks. I'll take a better look to this patch then apply. There maybe
> the same issue in the ppc64 strucutre ?
Yes, it looks like the same changes it needed in linux-user/ppc64/termbits.h
as well.
Stuart
Stuart R. Anderson anderson@netsweng.com
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
prev parent reply other threads:[~2007-04-18 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 20:20 [Qemu-devel] [PATCH] PPC termios structure ordering Stuart Anderson
2007-04-18 18:34 ` J. Mayer
2007-04-18 18:47 ` Stuart Anderson [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=Pine.LNX.4.64.0704181447220.22280@trantor.stuart.netsweng.com \
--to=anderson@netsweng.com \
--cc=l_indien@magic.fr \
--cc=qemu-devel@nongnu.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).