From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: edgar.iglesias@xilinx.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH net v1 1/1] net: xilinx_ethlite: Fix Rx-pong interrupt
Date: Tue, 6 May 2014 14:13:45 +0200 [thread overview]
Message-ID: <20140506121345.GF15810@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cf95edd0d1c0901fcf2922b232fda432360c1fd6.1399342093.git.peter.crosthwaite@xilinx.com>
On Mon, May 05, 2014 at 09:39:38PM -0700, Peter Crosthwaite wrote:
> There is no CTRL_I bit in the pong buffer control register. The
> CTRL_I bit from the ping buffer masks both ping and pong buffers.
> Fix.
>
> Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> ---
>
> hw/net/xilinx_ethlite.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Unfamiliar with the device but the patch itself looks clean. I'll drop
it from my queue if there are comments.
Thanks, applied to my net tree:
https://github.com/stefanha/qemu/commits/net
Stefan
prev parent reply other threads:[~2014-05-06 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 4:39 [Qemu-devel] [PATCH net v1 1/1] net: xilinx_ethlite: Fix Rx-pong interrupt Peter Crosthwaite
2014-05-06 12:13 ` Stefan Hajnoczi [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=20140506121345.GF15810@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=edgar.iglesias@xilinx.com \
--cc=peter.crosthwaite@xilinx.com \
--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).