qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bill Paul <wpaul@windriver.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug report + fix: e1000.c in 0.10.5 does not properly emulate real hardware
Date: Tue, 28 Jul 2009 15:21:12 -0700	[thread overview]
Message-ID: <200907281521.12322.wpaul@windriver.com> (raw)
In-Reply-To: <4A6F74D3.5080405@codemonkey.ws>

Of all the gin joints in all the towns in all the world, Anthony Liguori had 
to walk into mine and say:

> Bill Paul wrote:
> > Hi guys:
> >
> > I submitted a patch for e1000.c a while ago, to fix issues with the ICS
> > and EERD registers not being emulated properly, which I discovered while
> > testing QEMU with VxWorks. I provided binary VxWorks images and a
> > bootable bootrom floppy that works with QEMU for testing, but so far I
> > haven't heard anything further on this issue. I looked at the git
> > repository, and it doesn't look like the patch I submitted has been
> > applied yet.
> >
> > Does anyone have an update on this? Just checking to make sure the patch
> > doesn't fall through the cracks.
>
> I see you sent out a version with a Signed-off-by, but you didn't send
> it as a top-level patch.
>
> Please resend it as a top level patch (a new subject starting with
> [PATCH]) and that will get the ball rolling.

Let me make sure I understand correctly.

You must have my previous e-mail with the patch in front of you, with the 
attached unified diff. Are you saying that rather than just taking that 
unidiff, from the e-mail I already sent, you want me to send you exactly the 
same file, only with a different subject line that starts with [PATCH]?

I'd like to point out that a) while this may be part of some standardized 
project etiquette, I've yet to see these required steps clearly spelled out 
anywhere, and b) why can't you just take the diff I already sent and 
apply/test/molest/etc it now that you have it?

-Bill

> Regards,
>
> Anthony Liguori
>
> > -Bill

-- 
=============================================================================
-Bill Paul            (510) 749-2329 | Senior Engineer, Master of Unix-Fu
                 wpaul@windriver.com | Wind River Systems
=============================================================================
   "I put a dollar in a change machine. Nothing changed." - George Carlin
=============================================================================

  reply	other threads:[~2009-07-28 22:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  1:48 [Qemu-devel] bug report + fix: e1000.c in 0.10.5 does not properly emulate real hardware Bill Paul
2009-06-09  2:07 ` Anthony Liguori
2009-06-09  3:39   ` Bill Paul
2009-06-09 14:59     ` Richard W.M. Jones
2009-06-09 19:42       ` Bill Paul
2009-07-28 21:17         ` Bill Paul
2009-07-28 21:59           ` Anthony Liguori
2009-07-28 22:21             ` Bill Paul [this message]
2009-07-28 22:54               ` Anthony Liguori
2009-07-29 18:09                 ` Bill Paul

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=200907281521.12322.wpaul@windriver.com \
    --to=wpaul@windriver.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.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 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).