Skip to contentSkip to conversation

arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: implic

PATCH In review Fengguang Wu 3 participants 6 messages Sep 11, 2012 – Sep 13, 2012 Kernel janitors

lore
Share & tools
lore
#0 lore raw

PATCH 5/5 arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: implic

Hi Gavin,

FYI, kernel build failed on

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/gavin-window-alignment
head:   4814ef2ec1b8ebaabfc54bb50578313c2f94119a
commit: 4814ef2ec1b8ebaabfc54bb50578313c2f94119a [5/5] powerpc/powernv: I/O and memory alignment for P2P bridges
config: powerpc-allmodconfig

All related error/warning messages:

arch/powerpc/platforms/powernv/pci-ioda.c: In function 'pnv_pci_window_alignment':
arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: implicit declaration of function 'pci_pcie_type' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors

vim +1164 arch/powerpc/platforms/powernv/pci-ioda.c
1159 struct pnv_phb *phb = hose->private_data;
1160 int num_pci_bridges = 0;
1161
1162 bridge = bus->self;
1163 while (bridge) {

Quoted 1 line

1164 if (pci_pcie_type(bridge) = PCI_EXP_TYPE_PCI_BRIDGE) {

1165 num_pci_bridges++;
1166 if (num_pci_bridges >= 2)
1167 return 1;
1168 }
1169

---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <[email protected]> Intel Corporation

#1 lore raw

Re: [pci:pci/gavin-window-alignment 5/5] arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: im

Quoted 9 lines · Fengguang Wu

Hi Gavin,

FYI, kernel build failed on

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/gavin-window-alignment
head:   4814ef2ec1b8ebaabfc54bb50578313c2f94119a
commit: 4814ef2ec1b8ebaabfc54bb50578313c2f94119a [5/5] powerpc/powernv: I/O and memory alignment for P2P bridges
config: powerpc-allmodconfig
Quoted 5 lines

All related error/warning messages:

arch/powerpc/platforms/powernv/pci-ioda.c: In function 'pnv_pci_window_alignment':
arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: implicit declaration of function 'pci_pcie_type' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors

Sorry, this is my fault. I fixed this earlier, but I did it the wrong way.

What I did before was just update the patch in the pci/gavin-window-alignment branch. But what I should have done was to rebase that branch on top of pci/jiang-pcie-cap, which the branch it actually depends on (that's where pci_pcie_type() was added).

So I did that rebase and pushed both pci/gavin-window-alignment and next again. I think the result is sensible now.

Sorry for the mess.

Bjorn

Quoted 16 lines

vim +1164 arch/powerpc/platforms/powernv/pci-ioda.c
1159 struct pnv_phb *phb = hose->private_data;
1160 int num_pci_bridges = 0;
1161
1162 bridge = bus->self;
1163 while (bridge) {

Quoted 1 line

1164 if (pci_pcie_type(bridge) = PCI_EXP_TYPE_PCI_BRIDGE) {

1165 num_pci_bridges++;
1166 if (num_pci_bridges >= 2)
1167 return 1;
1168 }
1169

---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <[email protected]> Intel Corporation

#2 lore raw

Re: [pci:pci/gavin-window-alignment 5/5] arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: im

In reply to Fengguang Wu
Quoted 3 lines · Bjorn Helgaas

So I did that rebase and pushed both pci/gavin-window-alignment and next again. I think the result is sensible now.

Argh ... a rebase ! Oh well, thankfully I haven't pushed out yet, so I can reconstruct my tree.

Ben.

#3 lore raw

Re: [pci:pci/gavin-window-alignment 5/5] arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: im

In reply to Fengguang Wu
Quoted 10 lines · Bjorn Helgaas

Sorry, this is my fault. I fixed this earlier, but I did it the wrong way.

What I did before was just update the patch in the pci/gavin-window-alignment branch. But what I should have done was to rebase that branch on top of pci/jiang-pcie-cap, which the branch it actually depends on (that's where pci_pcie_type() was added).

So I did that rebase and pushed both pci/gavin-window-alignment and next again. I think the result is sensible now.

The result has content conflicts against a couple of drivers. If I fix that up locally that means that things might end up being a bit more complicated than expected when reconciling everything with Linus and that worries me.

Any chance you can pull in a recent Linus tree & fixup the merges before I pull that in myself ?

Cheers,
Ben.

#4 lore raw

Re: [pci:pci/gavin-window-alignment 5/5] arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: im

In reply to Fengguang Wu
Quoted 12 lines · Benjamin Herrenschmidt
Quoted 10 lines · Bjorn Helgaas

Sorry, this is my fault. I fixed this earlier, but I did it the wrong way.

What I did before was just update the patch in the pci/gavin-window-alignment branch. But what I should have done was to rebase that branch on top of pci/jiang-pcie-cap, which the branch it actually depends on (that's where pci_pcie_type() was added).

So I did that rebase and pushed both pci/gavin-window-alignment and next again. I think the result is sensible now.

Quoted 7 lines

The result has content conflicts against a couple of drivers. If I fix that up locally that means that things might end up being a bit more complicated than expected when reconciling everything with Linus and that worries me.

Any chance you can pull in a recent Linus tree & fixup the merges before I pull that in myself ?

I merged v3.6-rc5 into my "next" branch, fixed the conflicts in

drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c drivers/rapidio/devices/tsi721.c

and pushed the result. Let me know if this is not what you expected.

Bjorn

#5 lore raw

Re: [pci:pci/gavin-window-alignment 5/5] arch/powerpc/platforms/powernv/pci-ioda.c:1164:3: error: im

In reply to Fengguang Wu
Quoted 6 lines · Bjorn Helgaas

I merged v3.6-rc5 into my "next" branch, fixed the conflicts in

drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c drivers/rapidio/devices/tsi721.c

and pushed the result. Let me know if this is not what you expected.

Thanks. I'll end up pulling your entire next branch then. Unless you can do the same exercise in the topic branch I'm interested in :-)

Cheers,
Ben.