Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp828862imm; Wed, 26 Sep 2018 07:25:50 -0700 (PDT) X-Google-Smtp-Source: ACcGV60MV+p1+2wxI5TB6ML2EpuEmopbtCADBve6p4Gn8wHR4wlFilE45NYub+zvVJsZHcyyBuY5 X-Received: by 2002:a63:91c9:: with SMTP id l192-v6mr6044980pge.433.1537971950809; Wed, 26 Sep 2018 07:25:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537971950; cv=none; d=google.com; s=arc-20160816; b=fWezJnL4qVKI8McINliPbSK6a/94gHrYSuUiTtZO5IpYsY8Yyz5mVZedV2nHl/Ufj2 RPM+yV8QPbdtsxv+MP11/s2DaV4hs2blHJRA+0JYOsEzh7LhqHVrBCvUeQMGBFhVAtKH lOUztzlFxhW2LW6BciCmJRwB6PgXWIEnKODd6kKFaI436y/CiwloQaarA7HKrRCHsnFA sG78pgtmEHwH60L6ENzBuZ+toocBciVguU07iNn4ZnElNwH8HzXvvs3Ras48XzM1Mivk IayOh3dnEojgG0cs4n4vYpBUAlz6qfAjOFzAiFriYlem5W9eetzPa/CATaXtVSTjkyeJ LlSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=uY5g49Wed/iaEf+WGb7+8JrNGQhJKkq2vTYov4cx1oU=; b=FP43jXym5WuvubbR+/QizoTQE8m58hXg5GDKYO2RsAJ3RGk9OO8myme2G7+5lWUfXW b3xT/fcyysUow4H/iJdCKpVURkoEkXKM7PrRoMHuIyo0bbgEISKZK1CCNx8dHzbLfJaG OWAq423F54gDdLI/McB9t8Mi1miw+yq/uJhCimZooW7n4kDCBN5hCo2FbGB/fe1aEuqR epUup82IMz5MLSmUo0i9gvRP57IVyUrrgHtHa3kxWMyvM+ruDyZv0EBQHHil5IaI4ylR ZvWRu6B8EsDd4kSdTbC06siBqWzRF4Fy7Hsc871hoI2B0KgdEtbCI3kiOugSEK0lwD7y a7Wg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u10-v6si5600555plq.1.2018.09.26.07.25.33; Wed, 26 Sep 2018 07:25:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728298AbeIZUgq (ORCPT + 99 others); Wed, 26 Sep 2018 16:36:46 -0400 Received: from mga07.intel.com ([134.134.136.100]:20753 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727504AbeIZUgp (ORCPT ); Wed, 26 Sep 2018 16:36:45 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2018 07:23:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,306,1534834800"; d="scan'208";a="73038201" Received: from unknown (HELO localhost.localdomain) ([10.232.112.44]) by fmsmga007.fm.intel.com with ESMTP; 26 Sep 2018 07:23:32 -0700 Date: Wed, 26 Sep 2018 08:25:40 -0600 From: Keith Busch To: Stephen Rothwell Cc: Bjorn Helgaas , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: build failure after merge of the pci tree Message-ID: <20180926142540.GB14407@localhost.localdomain> References: <20180926150051.6ee97aae@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180926150051.6ee97aae@canb.auug.org.au> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 26, 2018 at 03:00:51PM +1000, Stephen Rothwell wrote: > Hi Bjorn, > > After merging the pci tree, today's linux-next build (powerpc allnoconfig) > failed like this: > > ld: drivers/pci/pci.o: in function `pci_bus_error_reset': > pci.c:(.text+0x5fba): undefined reference to `pci_slot_mutex' > ld: pci.c:(.text+0x5fc2): undefined reference to `pci_slot_mutex' > > Caused by commit > > 131b0ca2c7b2 ("PCI/ERR: Use slot reset if available") > > I have applied the following hack for today (there is probably a better > way): Thanks for the notice. Does this mean you don't have CONFIG_SYSFS? I must admit I missed that connection for building slot.c. > From: Stephen Rothwell > Date: Wed, 26 Sep 2018 14:55:37 +1000 > Subject: [PATCH] pci: move pci_slot_mutex so it is available where needed > > Fixes: 131b0ca2c7b2 ("PCI/ERR: Use slot reset if available") > Signed-off-by: Stephen Rothwell > --- > drivers/pci/pci.c | 2 ++ > drivers/pci/slot.c | 1 - > 2 files changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c > index 8c1e99a637d8..1fa67db6b21e 100644 > --- a/drivers/pci/pci.c > +++ b/drivers/pci/pci.c > @@ -5190,6 +5190,8 @@ static int pci_bus_reset(struct pci_bus *bus, int probe) > return ret; > } > > +DEFINE_MUTEX(pci_slot_mutex); > + > /** > * pci_bus_error_reset - reset the bridge's subordinate bus > * @bridge: The parent device that connects to the bus to reset > diff --git a/drivers/pci/slot.c b/drivers/pci/slot.c > index 3da03fcc6fbf..c46d5e1ff536 100644 > --- a/drivers/pci/slot.c > +++ b/drivers/pci/slot.c > @@ -14,7 +14,6 @@ > > struct kset *pci_slots_kset; > EXPORT_SYMBOL_GPL(pci_slots_kset); > -DEFINE_MUTEX(pci_slot_mutex); > > static ssize_t pci_slot_attr_show(struct kobject *kobj, > struct attribute *attr, char *buf) > -- > 2.18.0