Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754569AbXJWXEU (ORCPT ); Tue, 23 Oct 2007 19:04:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752781AbXJWXEJ (ORCPT ); Tue, 23 Oct 2007 19:04:09 -0400 Received: from mga03.intel.com ([143.182.124.21]:61819 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752728AbXJWXEI (ORCPT ); Tue, 23 Oct 2007 19:04:08 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.21,320,1188802800"; d="scan'208";a="304232210" Message-ID: <471E7DCA.9030700@intel.com> Date: Tue, 23 Oct 2007 16:03:38 -0700 From: "Kok, Auke" User-Agent: Thunderbird 2.0.0.6 (X11/20070911) MIME-Version: 1.0 To: Dave Jones , Jeff Garzik , "Kok, Auke" , Adam Jackson , linux-kernel@vger.kernel.org, David Miller , netdev Subject: Re: [PATCH] Add eeprom_bad_csum_allow module option to e1000. References: <11931515302013-git-send-email-ajax@redhat.com> <471E1ECD.80002@intel.com> <1193156487.26974.39.camel@localhost.localdomain> <471E2AD0.1000500@intel.com> <471E5C21.8030908@garzik.org> <20071023212026.GF7793@redhat.com> In-Reply-To: <20071023212026.GF7793@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1369 Lines: 30 Dave Jones wrote: > On Tue, Oct 23, 2007 at 04:40:01PM -0400, Jeff Garzik wrote: > > > > In any case, this patch should not be merged. We often send it around to users to > > > debug their issue in case it involves eeproms, but merging it will just conceal > > > the real issue and all of a sudden a flood of people stop reporting *real* issues > > > to us. > > > > Sorry, I disagree. Just as with e100, if there is a clear way the user > > can recover their setup -- and Adam says his was effective -- I don't > > see why we should be denying users the ability to use their own hardware. > > Indeed. This is a common enough problem that not including it causes more pain > than its worth. I have two affected boxes myself that I actually thought > the hardware was dead before I tried ajax's patch. look: You should have reported this to us and you didn't. Now you are using the fact that you did not report it as an argument which is out of place. why do you say it is common? how often have you seen this and not reported it back to our support? are you willingly trying to frustrate this issue? Auke - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/