qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lonnie Mendez <lmendez19@austin.rr.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Large USB-Patch Documentation and todays CVS patch
Date: Thu, 27 Apr 2006 01:16:42 -0500	[thread overview]
Message-ID: <445061CA.7070605@austin.rr.com> (raw)
In-Reply-To: <13040.1146091241@www072.gmx.net>

Johannes Schindelin wrote:

>I am quite sure you put a lot of work into this patch, but you sure make it
>hard to appreciate, too.
>
>First note that applying such a huge patch is bad. Let me help you (a little
>more than last time) to understand that: You are almost guaranteed to
>introduce bugs, and what's worse, regressions. Because it is so huge, you
>are further guaranteed to have a real hard time tracking that regression.
>  
>
   Seeing as there is a release coming up this is most definitely not a 
good thing.  Initial testing yielded lots of this. 

   I'd like to see my all-in-one patch stripped out.  Then simply 
modifying the linux redirector to support the improved error handling 
(have it clear endpoint halt/etc) and other improvements.  Later, the 
new redirectors can be merged in and modified as necessary.

   The purpose of modifying the user interface to the usb layer also 
confuses me.  What was the reasoning behind changing host:busaddr.addr 
to host:busaddr:addr and host:VID:PID to host:VIDxPID?  This is 
something that should be abstracted in the layer and not handed down to 
the user.  Why display the bcdUSB revision and not the connected speed 
to the user (as is already done)?

   To argue that this must all go in at once or none at all is silly.  
I've seen the changes and know that my redirectors aren't necessary for 
this to function.  I'm not trying to get anyone down on this but am just 
saying this needs more discussion and thought.

  parent reply	other threads:[~2006-04-27  6:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 16:19 [Qemu-devel] Large USB-Patch Documentation and todays CVS patch nix.wie.weg
2006-04-26 22:40 ` Johannes Schindelin
2006-04-27  1:23   ` nix.wie.weg
2006-04-27  8:37     ` andrzej zaborowski
2006-04-27  9:48     ` Johannes Schindelin
2006-04-27 13:29       ` Lonnie Mendez
2006-04-27 15:30       ` nix.wie.weg
2006-04-27  6:16   ` Lonnie Mendez [this message]
2006-04-27 15:45     ` nix.wie.weg
2006-04-28 12:44       ` Joseph Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-05-23 11:23 Per Åstrand

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=445061CA.7070605@austin.rr.com \
    --to=lmendez19@austin.rr.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).