From: Nathan Froyd <froydnj@codesourcery.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] linux-user: ppc signal handling
Date: Thu, 23 Apr 2009 09:11:13 -0700 [thread overview]
Message-ID: <20090423161113.GU22588@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904231843130.2144@linmac.oyster.ru>
On Thu, Apr 23, 2009 at 06:44:39PM +0400, malc wrote:
> On Wed, 22 Apr 2009, Nathan Froyd wrote:
> > The first patch moves the cpu capability flags to a place where
> > save_user_regs and restore_user_regs can get at them.
>
> Thing is i applied patches 2 and 3 and things just worked thus questioned
> the utility of patch 1.
I suppose this is possible, but it seems unlikely, given that patches 2
and 3 reference env->insns_flags, which is a nonexistent field if you
didn't already apply patch 1...
-Nathan
next prev parent reply other threads:[~2009-04-23 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 2:32 [Qemu-devel] [PATCH 0/3] linux-user: add ppc signal handling Nathan Froyd
2009-04-22 2:32 ` [Qemu-devel] [PATCH 1/3] target-ppc: expose cpu capability flags Nathan Froyd
2009-04-22 2:32 ` [Qemu-devel] [PATCH 2/3] linux-user: ppc signal handling Nathan Froyd
2009-04-23 1:22 ` malc
2009-04-23 1:55 ` Nathan Froyd
2009-04-23 14:44 ` malc
2009-04-23 16:11 ` Nathan Froyd [this message]
2009-04-23 23:18 ` malc
2009-04-22 2:32 ` [Qemu-devel] [PATCH 3/3] linux-user: support ELF_HWCAP for PPPC Nathan Froyd
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 19:26 [Qemu-devel] [PATCH 0/3] linux-user: add ppc signal handling, v2 Nathan Froyd
2009-05-12 19:26 ` [Qemu-devel] [PATCH 2/3] linux-user: ppc signal handling Nathan Froyd
2009-05-13 2:13 ` Nathan Froyd
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=20090423161113.GU22588@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=av1474@comtv.ru \
--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).