qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Weil <weil@mail.berlios.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] eepro100: Restructure code (new function tx_command)
Date: Sat, 12 Dec 2009 09:21:02 -0600	[thread overview]
Message-ID: <4B23B4DE.2060604@codemonkey.ws> (raw)
In-Reply-To: <4B23A2A6.5020201@mail.berlios.de>

Stefan Weil wrote:
> Stefan Weil schrieb:
>   
>> Handling of transmit commands is rather complex,
>> so about 80 lines of code were moved from function
>> action_command to the new function tx_command.
>>
>> The two new values "tx" and "cb_address" in the
>> eepro100 status structure made this possible without
>> passing too many parameters.
>>
>> In addition, the moved code was cleaned a little bit:
>> old comments marked with //~ were removed, C++ style
>> comments were replaced by C style comments, C++ like
>> variable declarations after code were reordered.
>>
>> Simplified mode is still broken. Nor did I fix
>> endianess issues. Both problems will be fixed in
>> additional patches (which need this one).
>>
>> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
>> ---
>> hw/eepro100.c | 192
>> +++++++++++++++++++++++++++++----------------------------
>> 1 files changed, 98 insertions(+), 94 deletions(-)
>>     
>
> This patch is still missing in QEMU master.
> Because of other patches (which were sent later!), a rebase is needed again
> (it was rebased 3 times now). Only the line with qemu_send_packet changed.
>
> Please apply the rebased patch if there are no really important
> reasons against it (there are none), hopefully without waiting several
> weeks again.
> It is needed for very important bug fixes (multicast, simple transmit mode).
>   

Michael had given the patch some feedback that I think is valuable.  I 
haven't seen a response to his feedback nor have I seen a resubmit 
incorporating the feedback.

Storing intermediate state of a function as global state (instead of on 
the stack) is odd.  Even if there's a great justification (I don't think 
there is), such a thing is sufficiently unusual that it deserves a 
better comment.

BTW, part of the trouble your having is you're sending one patch that 
does too many things.  If you submitted a series that contained code 
cleanups, and then code motion, the first patches would have been no 
brainers to commit while the code motion would have been treated 
separately making rebasing less painful.

Regards,

Anthony Liguori

      parent reply	other threads:[~2009-12-12 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 20:54 [Qemu-devel] [PATCH] eepro100: Restructure code (new function tx_command) Stefan Weil
2009-11-30  9:30 ` [Qemu-devel] " Michael S. Tsirkin
2009-11-30 17:05   ` Stefan Weil
2009-11-30 20:39     ` Michael S. Tsirkin
2009-12-12 19:45       ` Stefan Weil
2009-12-13  8:18         ` Michael S. Tsirkin
2009-12-13 20:59           ` Stefan Weil
2009-12-13 21:36             ` Michael S. Tsirkin
2009-12-14  9:25               ` [Qemu-devel] [PATCH] eepro100: Better documentation for temporary data Stefan Weil
2009-12-15 15:49                 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-12 14:03 ` [Qemu-devel] Re: [PATCH] eepro100: Restructure code (new function tx_command) Stefan Weil
2009-12-12 14:05   ` [Qemu-devel] " Stefan Weil
2009-12-12 15:21   ` Anthony Liguori [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=4B23B4DE.2060604@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).