From: Richard Henderson <rth@twiddle.net>
To: Stafford Horne <shorne@gmail.com>
Cc: Jia Liu <proljc@gmail.com>,
qemu-devel@nongnu.org, openrisc@lists.librecores.org
Subject: Re: [Qemu-devel] [PATCH] target-openrisc: Fix exception handling status registers
Date: Mon, 6 Feb 2017 18:36:04 -0800 [thread overview]
Message-ID: <fbaa2670-fa68-4c31-6197-bef2b5eb752c@twiddle.net> (raw)
In-Reply-To: <20170203151449.GC32144@lianli.shorne-pla.net>
On 02/03/2017 07:14 AM, Stafford Horne wrote:
> I tried your tgt-or1k-2 branch with my latest kernel and have no issues.
Ok, excellent, thanks. I'll send a pull for that branch then.
r~
WARNING: multiple messages have this Message-ID (diff)
From: Richard Henderson <rth@twiddle.net>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [Qemu-devel] [PATCH] target-openrisc: Fix exception handling status registers
Date: Mon, 6 Feb 2017 18:36:04 -0800 [thread overview]
Message-ID: <fbaa2670-fa68-4c31-6197-bef2b5eb752c@twiddle.net> (raw)
In-Reply-To: <20170203151449.GC32144@lianli.shorne-pla.net>
On 02/03/2017 07:14 AM, Stafford Horne wrote:
> I tried your tgt-or1k-2 branch with my latest kernel and have no issues.
Ok, excellent, thanks. I'll send a pull for that branch then.
r~
next prev parent reply other threads:[~2017-02-07 2:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 21:57 [OpenRISC] [PATCH] target-openrisc: Fix exception handling status registers Stafford Horne
2017-01-13 22:02 ` Stafford Horne
2017-01-14 4:29 ` Jia Liu
2017-01-14 8:04 ` [Qemu-devel] " Stafford Horne
2017-01-14 8:04 ` [OpenRISC] " Stafford Horne
2017-01-20 16:39 ` [Qemu-devel] " Stafford Horne
2017-01-20 16:39 ` [OpenRISC] " Stafford Horne
2017-01-23 18:08 ` [Qemu-devel] " Richard Henderson
2017-01-23 18:08 ` [OpenRISC] " Richard Henderson
2017-01-24 10:26 ` Stafford Horne
2017-01-24 10:26 ` [OpenRISC] " Stafford Horne
2017-01-24 18:32 ` Richard Henderson
2017-01-24 18:32 ` [OpenRISC] " Richard Henderson
2017-01-25 12:34 ` Stafford Horne
2017-01-25 12:34 ` [OpenRISC] " Stafford Horne
2017-01-25 17:27 ` Richard Henderson
2017-01-25 17:27 ` [OpenRISC] " Richard Henderson
2017-01-26 13:12 ` Stafford Horne
2017-01-26 13:12 ` [OpenRISC] " Stafford Horne
2017-01-26 17:26 ` Richard Henderson
2017-01-26 17:26 ` [OpenRISC] " Richard Henderson
2017-01-26 22:01 ` Stafford Horne
2017-01-26 22:01 ` [OpenRISC] " Stafford Horne
2017-02-01 10:04 ` Stafford Horne
2017-02-01 10:04 ` [OpenRISC] " Stafford Horne
2017-02-01 18:15 ` Richard Henderson
2017-02-01 18:15 ` [OpenRISC] " Richard Henderson
2017-02-02 14:34 ` Stafford Horne
2017-02-02 14:34 ` [OpenRISC] " Stafford Horne
2017-02-03 15:14 ` Stafford Horne
2017-02-03 15:14 ` [OpenRISC] " Stafford Horne
2017-02-07 2:36 ` Richard Henderson [this message]
2017-02-07 2:36 ` Richard Henderson
2017-02-06 20:44 ` Richard Henderson
2017-02-07 0:31 ` Stafford Horne
2017-02-07 5:48 ` Richard Henderson
2017-02-07 5:53 ` Richard Henderson
2017-02-07 5:53 ` [OpenRISC] " Richard Henderson
2017-02-08 14:01 ` Stafford Horne
2017-02-08 14:01 ` [OpenRISC] " Stafford Horne
2017-02-08 16:38 ` Stafford Horne
2017-02-08 16:38 ` [OpenRISC] " Stafford Horne
2017-02-08 20:38 ` Richard Henderson
2017-02-08 20:38 ` [OpenRISC] " Richard Henderson
2017-01-13 22:00 Stafford Horne
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=fbaa2670-fa68-4c31-6197-bef2b5eb752c@twiddle.net \
--to=rth@twiddle.net \
--cc=openrisc@lists.librecores.org \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=shorne@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.