From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760874AbYDKQhp (ORCPT ); Fri, 11 Apr 2008 12:37:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760171AbYDKQhe (ORCPT ); Fri, 11 Apr 2008 12:37:34 -0400 Received: from mga01.intel.com ([192.55.52.88]:43660 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758329AbYDKQhd (ORCPT ); Fri, 11 Apr 2008 12:37:33 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.25,642,1199692800"; d="scan'208";a="549969770" Message-ID: <47FF9060.5040202@intel.com> Date: Fri, 11 Apr 2008 09:22:56 -0700 From: "Kok, Auke" User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Ingo Molnar CC: Christoph Hellwig , Jeff Garzik , Matthew Wilcox , Linux Kernel Mailing List , NetDev , e1000-list , linux-pci maillist , Andrew Morton , "David S. Miller" , Linus Torvalds , Jesse Brandeburg , "Ronciak, John" , "Allan, Bruce W" , Greg KH , Arjan van de Ven , "Rafael J. Wysocki" Subject: Re: [patch] e1000=y && e1000e=m regression fix References: <47FBD34A.6080508@garzik.org> <20080408203314.GA28952@elte.hu> <47FBDBE9.9040700@garzik.org> <20080409193850.GA11763@elte.hu> <47FD2325.2030705@intel.com> <47FE5C89.5060209@intel.com> <20080410192714.GA14055@elte.hu> <47FE8566.5040809@intel.com> <20080411112653.GC9205@elte.hu> <20080411113644.GA7767@infradead.org> <20080411121606.GA25661@elte.hu> In-Reply-To: <20080411121606.GA25661@elte.hu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Apr 2008 16:23:36.0206 (UTC) FILETIME=[6495E2E0:01C89BF0] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ingo Molnar wrote: > i dont really care _how_ this gets solved - i'm not maintaining this > code. What forced me to deal with it was this outright denial of my > problem, the ridiculing and NACK-ing of it and general stonewalling. this is a gross misrepresentation and misunderstanding. You're completely ignoring the fact that: (1) I debated whether it was a "regression" - in my opinion design changes that deliberately break things are hardly worth this incredibly negative stamp (2) I never NACK'ed your patch. I just withdrew my ack. (3) You're stonewalling me by pretty much forcing me to completely drop the driver split and not showing any understanding for the reason behind the split at all. You don't provide a solution, nor does anyone, and I don't see any solution to what you want but to completely cancel this driver split. And I'm _not_ going to do that.