Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755035AbYJCA31 (ORCPT ); Thu, 2 Oct 2008 20:29:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753836AbYJCA3T (ORCPT ); Thu, 2 Oct 2008 20:29:19 -0400 Received: from www.tglx.de ([62.245.132.106]:56494 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753795AbYJCA3S (ORCPT ); Thu, 2 Oct 2008 20:29:18 -0400 Date: Fri, 3 Oct 2008 02:28:03 +0200 (CEST) From: Thomas Gleixner To: Jesse Brandeburg cc: Linus Torvalds , Andrew Morton , Olaf Kirch , Jiri Kosina , Jesse Brandeburg , LKML , linux-netdev@vger.kernel.org, kkeil@suse.de, agospoda@redhat.com, arjan@linux.intel.com, david.graham@intel.com, bruce.w.allan@intel.com, john.ronciak@intel.com, chris.jones@canonical.com, tim.gardner@intel.com, airlied@gmail.com, Ingo Molnar Subject: Re: [PATCH] e1000e: prevent concurrent access to NVRAM In-Reply-To: <4807377b0810021719m164e734cndaddb7006508cabc@mail.gmail.com> Message-ID: References: <20080930030825.22950.18891.stgit@jbrandeb-bw.jf.intel.com> <20080930031952.22950.45228.stgit@jbrandeb-bw.jf.intel.com> <200810021703.43770.okir@suse.de> <4807377b0810021719m164e734cndaddb7006508cabc@mail.gmail.com> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1060 Lines: 26 On Thu, 2 Oct 2008, Jesse Brandeburg wrote: > On Thu, Oct 2, 2008 at 4:42 PM, Thomas Gleixner wrote: > > The confirmed bugs where the nvram acquire code was called > > concurrently are still in your tree and the prevention patch along > > with the resulting bugfixes are stuck in some obscure intel QA > > process. > > > > Please apply at least the bug prevention patch below. > > This is the same patch I posted 7 minutes ago, except that this patch > without the e1000e changes applied before it will cause all sorts of > WARN's to be printed during normal operation. If at all possible I > think they should stay together as a group to prevent un-necessary > noise in the logs. Sure, I'm all for the combo of those. I just wanted to get some motion into this stale process. tglx -- 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/