Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KzU3T-00052Q-GI for qemu-devel@nongnu.org; Mon, 10 Nov 2008 05:31:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KzU3R-000527-L2 for qemu-devel@nongnu.org; Mon, 10 Nov 2008 05:31:35 -0500 Received: from [199.232.76.173] (port=38019 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KzU3R-000524-HO for qemu-devel@nongnu.org; Mon, 10 Nov 2008 05:31:33 -0500 Received: from batfish.pepperfish.net ([87.237.62.180]:34760 helo=flounder.pepperfish.net) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KzU3R-0002f8-55 for qemu-devel@nongnu.org; Mon, 10 Nov 2008 05:31:33 -0500 Received: from cpc2-asht1-0-0-cust815.manc.cable.ntl.com ([80.5.55.48] helo=[10.19.3.101]) by flounder.pepperfish.net with esmtpsa (Exim 4.68 #1 (Debian)) id 1KzU3O-0003Ar-RV for ; Mon, 10 Nov 2008 10:31:30 +0000 Subject: Re: [Qemu-devel] [PATCH] DM9000 network card driver From: Daniel Silverstone In-Reply-To: <1225104596.24465.3.camel@petitemort> References: <1225104596.24465.3.camel@petitemort> Content-Type: text/plain Date: Mon, 10 Nov 2008 10:31:29 +0000 Message-Id: <1226313089.10490.3.camel@petitemort> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: dsilvers@simtec.co.uk, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, 2008-10-27 at 10:49 +0000, Daniel Silverstone wrote: > I think this fell through the cracks, so here it is again. > The Davicom DM9000 10/100 Ethernet controller. I don't see any replies to this -- it's possible that my list subscription was playing up at the time, so I thought I'd re-poke about it. Basically I'm desperate to know if I'm even going the right way in my patches -- am I getting them to a state where they could be merged, or am I wasting my time? Is there an FAQ I need to read which will tell me how to present these patches in a way which is easier for you all to deal with them? I'm just somewhat disheartened that I see patches turn up and get discussed strongly, and then the updated patches end up being merged, where after the initial discussion, this patch kinda got dropped on the floor without an explicit "no" or anything; sitting for two weeks untouched on-list. I appreciate that you're all busy, so if the answer is simply "You're on the list, just it'll be a while" then at least I can carry that back to my boss who wants to know how it's going getting these patches to you. Regards, Daniel. -- Daniel Silverstone http://www.simtec.co.uk/ PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895