From: Stephen Rothwell <sfr@canb.auug.org.au> To: Bjorn Helgaas <bhelgaas@google.com> Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>, "David S. Miller" <davem@davemloft.net>, sparclinux@vger.kernel.org Subject: linux-next: build failure after merge of the final tree (pci tree related) Date: Tue, 12 Jun 2012 14:54:41 +1000 [thread overview] Message-ID: <20120612145441.400975347f06785d391d0f8f@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 1375 bytes --] Hi all, After merging the final tree, today's linux-next build (sparc64 defconfig) failed like this: arch/sparc/kernel/pci.c: In function 'pci_scan_one_pbm': arch/sparc/kernel/pci.c:689:21: error: 'struct pci_pbm_info' has no member named 'pci_last_busn' Caused by commit 2c7f691b032b ("sparc/PCI: register busn_res for root buses"). I have added the following patch for today: From: Stephen Rothwell <sfr@canb.auug.org.au> Date: Tue, 12 Jun 2012 14:48:39 +1000 Subject: [PATCH] sparc/PCI: fix typo Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au> --- arch/sparc/kernel/pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/sparc/kernel/pci.c b/arch/sparc/kernel/pci.c index 74e4bf3..4f92a9a 100644 --- a/arch/sparc/kernel/pci.c +++ b/arch/sparc/kernel/pci.c @@ -686,7 +686,7 @@ struct pci_bus * __devinit pci_scan_one_pbm(struct pci_pbm_info *pbm, pci_add_resource_offset(&resources, &pbm->mem_space, pbm->mem_space.start); pbm->busn.start = pbm->pci_first_busno; - pbm->busn.end = pbm->pci_last_busn; + pbm->busn.end = pbm->pci_last_busno; pbm->busn.flags = IORESOURCE_BUS; pci_add_resource(&resources, &pbm->busn); bus = pci_create_root_bus(parent, pbm->pci_first_busno, pbm->pci_ops, -- 1.7.10.280.gaa39 -- Cheers, Stephen Rothwell sfr@canb.auug.org.au [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au> To: Bjorn Helgaas <bhelgaas@google.com> Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>, "David S. Miller" <davem@davemloft.net>, sparclinux@vger.kernel.org Subject: linux-next: build failure after merge of the final tree (pci tree related) Date: Tue, 12 Jun 2012 04:54:41 +0000 [thread overview] Message-ID: <20120612145441.400975347f06785d391d0f8f@canb.auug.org.au> (raw) In-Reply-To: <BANLkTim5dYNmTMJo-Wa3LYCTi4vxPGMNeQ@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1375 bytes --] Hi all, After merging the final tree, today's linux-next build (sparc64 defconfig) failed like this: arch/sparc/kernel/pci.c: In function 'pci_scan_one_pbm': arch/sparc/kernel/pci.c:689:21: error: 'struct pci_pbm_info' has no member named 'pci_last_busn' Caused by commit 2c7f691b032b ("sparc/PCI: register busn_res for root buses"). I have added the following patch for today: From: Stephen Rothwell <sfr@canb.auug.org.au> Date: Tue, 12 Jun 2012 14:48:39 +1000 Subject: [PATCH] sparc/PCI: fix typo Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au> --- arch/sparc/kernel/pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/sparc/kernel/pci.c b/arch/sparc/kernel/pci.c index 74e4bf3..4f92a9a 100644 --- a/arch/sparc/kernel/pci.c +++ b/arch/sparc/kernel/pci.c @@ -686,7 +686,7 @@ struct pci_bus * __devinit pci_scan_one_pbm(struct pci_pbm_info *pbm, pci_add_resource_offset(&resources, &pbm->mem_space, pbm->mem_space.start); pbm->busn.start = pbm->pci_first_busno; - pbm->busn.end = pbm->pci_last_busn; + pbm->busn.end = pbm->pci_last_busno; pbm->busn.flags = IORESOURCE_BUS; pci_add_resource(&resources, &pbm->busn); bus = pci_create_root_bus(parent, pbm->pci_first_busno, pbm->pci_ops, -- 1.7.10.280.gaa39 -- Cheers, Stephen Rothwell sfr@canb.auug.org.au [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-06-12 4:54 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-12 4:54 Stephen Rothwell [this message] 2012-06-12 4:54 ` linux-next: build failure after merge of the final tree (pci tree related) Stephen Rothwell 2012-06-12 15:31 ` Bjorn Helgaas 2012-06-12 15:31 ` Bjorn Helgaas 2012-06-12 15:31 ` Bjorn Helgaas 2012-06-13 0:50 ` Stephen Rothwell 2012-06-13 0:50 ` Stephen Rothwell 2012-06-13 23:20 ` Bjorn Helgaas 2012-06-13 23:20 ` Bjorn Helgaas -- strict thread matches above, loose matches on Subject: below -- 2017-11-30 3:46 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell 2017-11-30 3:46 ` Stephen Rothwell 2014-04-22 6:22 linux-next: build failure after merge of the audit tree Stephen Rothwell 2014-04-22 6:22 ` Stephen Rothwell 2014-04-22 15:56 ` Richard Guy Briggs 2014-04-22 15:56 ` Richard Guy Briggs 2014-04-22 16:32 ` Eric Paris 2014-04-22 16:32 ` Eric Paris 2014-04-22 21:27 ` Stephen Rothwell 2014-04-22 21:27 ` Stephen Rothwell 2013-02-11 7:34 linux-next: build failure after merge of the final tree (acpi tree related) Stephen Rothwell 2013-02-11 7:34 ` Stephen Rothwell 2013-02-11 18:22 ` Bjorn Helgaas 2013-02-11 18:22 ` Bjorn Helgaas 2013-02-11 23:23 ` Len Brown 2013-02-11 23:23 ` Len Brown 2013-02-12 17:35 ` Sam Ravnborg 2013-02-12 17:35 ` Sam Ravnborg 2013-02-12 18:01 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Len Brown 2013-02-12 18:01 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree r Len Brown 2013-02-12 18:03 ` Should SPARC use cpuidle? Len Brown 2013-02-12 18:03 ` Len Brown 2013-02-12 19:36 ` Sam Ravnborg 2013-02-12 19:36 ` Sam Ravnborg 2013-02-12 19:42 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Sam Ravnborg 2013-02-12 19:42 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tr Sam Ravnborg 2011-12-07 6:05 linux-next: build failure after merge of the final tree (pci tree related) Stephen Rothwell 2011-12-07 15:08 ` Bjorn Helgaas 2011-12-07 15:25 ` Bjorn Helgaas 2011-12-07 17:13 ` Jesse Barnes 2011-12-07 20:24 ` Stephen Rothwell 2011-12-08 19:01 ` Tony Luck 2011-12-09 3:53 ` Bjorn Helgaas 2011-12-09 20:02 ` Luck, Tony 2011-12-12 20:53 ` Jesse Barnes 2011-06-09 7:27 linux-next: build failure after merge of the final tree (staging related) Stephen Rothwell 2011-06-09 18:41 ` Greg KH 2011-06-09 19:22 ` Greg KH 2011-06-10 6:05 ` Stephen Rothwell 2011-06-10 6:09 ` Stephen Rothwell 2011-06-10 22:34 ` Greg KH 2011-06-15 4:21 ` Stephen Rothwell 2011-06-16 19:14 ` Greg KH 2011-06-23 0:35 ` Stephen Rothwell 2011-06-23 21:51 ` Greg KH 2011-06-24 0:00 ` Stephen Rothwell 2011-06-27 21:45 ` Greg KH 2011-06-28 0:16 ` Stephen Rothwell 2011-06-15 12:05 ` Geert Uytterhoeven 2011-06-15 12:05 ` Geert Uytterhoeven 2011-06-15 15:47 ` Greg KH 2011-06-15 15:47 ` linux-next: build failure after merge of the final tree (staging Greg KH 2011-06-15 14:35 ` [PATCH] arch/tile: remove useless set_fixmap_nocache() macro Chris Metcalf 2011-06-15 14:35 ` Chris Metcalf 2011-06-15 14:35 ` Chris Metcalf 2011-06-15 14:35 ` Chris Metcalf 2011-06-15 14:35 ` Chris Metcalf 2011-06-09 19:52 ` linux-next: build failure after merge of the final tree (staging related) Henry Ptasinski 2011-06-09 20:19 ` Greg KH
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20120612145441.400975347f06785d391d0f8f@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=bhelgaas@google.com \ --cc=davem@davemloft.net \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=sparclinux@vger.kernel.org \ --cc=yinghai@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.