Tree/Branch: next-20170621 Git describe: next-20170621 Commit: be285968cc Add linux-next specific files for 20170621
Build Time: 0 min 10 sec
Passed: 6 / 7 ( 85.71 %) Failed: 1 / 7 ( 14.29 %)
Errors: 2 Warnings: 7 Section Mismatches: 14
Failed defconfigs: arm-allmodconfig
Errors:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration] ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token
------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 2 warnings 0 mismatches : arm-multi_v5_defconfig 2 warnings 0 mismatches : arm-multi_v7_defconfig 2 warnings 0 mismatches : x86_64-defconfig 10 warnings 14 mismatches : arm-allmodconfig 2 warnings 0 mismatches : arm-allnoconfig 2 warnings 0 mismatches : x86_64-allnoconfig 2 warnings 0 mismatches : arm-multi_v4t_defconfig
-------------------------------------------------------------------------------
Errors summary: 2 6 ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token 1 ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
Warnings Summary: 7 7 ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable] 5 ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' declared 'static' but never defined [-Wunused-function] 4 ../kernel/cpu.c:1778:6: warning: unused variable 'cpu' [-Wunused-variable] 3 ../include/linux/printk.h:303:2: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' used but never defined 1 ../drivers/gpu/drm/arm/hdlcd_crtc.c:264:6: warning: unused variable 'src_x' [-Wunused-variable] 1 ../drivers/gpu/drm/arm/hdlcd_crtc.c:264:13: warning: unused variable 'src_y' [-Wunused-variable]
Section Mismatch Summary: 14 1 WARNING: drivers/clk/built-in.o(.text+0x150a4): Section mismatch in reference from the function sr_genpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/built-in.o(.text+0x15054): Section mismatch in reference from the function sr_genpll4_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/built-in.o(.text+0x14ffc): Section mismatch in reference from the function sr_genpll5_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/built-in.o(.text+0x14fa8): Section mismatch in reference from the function sr_lcpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/built-in.o(.text+0x14f58): Section mismatch in reference from the function sr_lcpll1_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/built-in.o(.text+0x14f08): Section mismatch in reference from the function sr_lcpll_pcie_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/built-in.o(.text+0x14ebc): Section mismatch in reference from the function sr_genpll3_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x46c4): Section mismatch in reference from the function sr_genpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x4674): Section mismatch in reference from the function sr_genpll4_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x461c): Section mismatch in reference from the function sr_genpll5_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x45c8): Section mismatch in reference from the function sr_lcpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x4578): Section mismatch in reference from the function sr_lcpll1_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x4528): Section mismatch in reference from the function sr_lcpll_pcie_clk_init() to the function .init.text:iproc_pll_clk_setup() 1 WARNING: drivers/clk/bcm/built-in.o(.text+0x44dc): Section mismatch in reference from the function sr_genpll3_clk_init() to the function .init.text:iproc_pll_clk_setup()
=============================================================================== Detailed per-defconfig build reports below:
------------------------------------------------------------------------------- arm-multi_v5_defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings: ../kernel/cpu.c:1778:6: warning: unused variable 'cpu' [-Wunused-variable] ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable]
------------------------------------------------------------------------------- arm-multi_v7_defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings: ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable] ../include/linux/printk.h:303:2: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]
------------------------------------------------------------------------------- x86_64-defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings: ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable] ../include/linux/printk.h:303:2: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]
------------------------------------------------------------------------------- arm-allmodconfig : FAIL, 7 errors, 10 warnings, 14 section mismatches
Errors: ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration] ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token
Warnings: ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable] ../include/linux/printk.h:303:2: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/gpu/drm/arm/hdlcd_crtc.c:264:13: warning: unused variable 'src_y' [-Wunused-variable] ../drivers/gpu/drm/arm/hdlcd_crtc.c:264:6: warning: unused variable 'src_x' [-Wunused-variable] ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' used but never defined ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' declared 'static' but never defined [-Wunused-function] ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' declared 'static' but never defined [-Wunused-function] ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' declared 'static' but never defined [-Wunused-function] ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' declared 'static' but never defined [-Wunused-function] ../include/linux/qed/qede_rdma.h:84:19: warning: 'qede_rdma_dev_add' declared 'static' but never defined [-Wunused-function]
Section Mismatches: WARNING: drivers/clk/bcm/built-in.o(.text+0x44dc): Section mismatch in reference from the function sr_genpll3_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/bcm/built-in.o(.text+0x4528): Section mismatch in reference from the function sr_lcpll_pcie_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/bcm/built-in.o(.text+0x4578): Section mismatch in reference from the function sr_lcpll1_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/bcm/built-in.o(.text+0x45c8): Section mismatch in reference from the function sr_lcpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/bcm/built-in.o(.text+0x461c): Section mismatch in reference from the function sr_genpll5_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/bcm/built-in.o(.text+0x4674): Section mismatch in reference from the function sr_genpll4_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/bcm/built-in.o(.text+0x46c4): Section mismatch in reference from the function sr_genpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x14ebc): Section mismatch in reference from the function sr_genpll3_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x14f08): Section mismatch in reference from the function sr_lcpll_pcie_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x14f58): Section mismatch in reference from the function sr_lcpll1_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x14fa8): Section mismatch in reference from the function sr_lcpll0_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x14ffc): Section mismatch in reference from the function sr_genpll5_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x15054): Section mismatch in reference from the function sr_genpll4_clk_init() to the function .init.text:iproc_pll_clk_setup() WARNING: drivers/clk/built-in.o(.text+0x150a4): Section mismatch in reference from the function sr_genpll0_clk_init() to the function .init.text:iproc_pll_clk_setup()
------------------------------------------------------------------------------- arm-allnoconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings: ../kernel/cpu.c:1778:6: warning: unused variable 'cpu' [-Wunused-variable] ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable]
------------------------------------------------------------------------------- x86_64-allnoconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings: ../kernel/cpu.c:1778:6: warning: unused variable 'cpu' [-Wunused-variable] ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable]
------------------------------------------------------------------------------- arm-multi_v4t_defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings: ../kernel/cpu.c:1778:6: warning: unused variable 'cpu' [-Wunused-variable] ../mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable] -------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host controller support).
Sorry for late reply,
+Lorenzo
On Wed, 2017-06-21 at 18:04 +0800, Mark Brown wrote:
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host controller support).
Hi Lorenzo,
I picked up your changes and had some modifications like what you did for other platforms:
9f8e3a5 PCI: Add devm_pci_alloc_host_bridge() interface 35a1a84 PCI: Add pci_free_host_bridge() interface e33aafd PCI: Initialize bridge release function at bridge allocation
...and it looks Okay.
I have also noticed that you continue sending patches for other platforms but I have not yet had a look in detail. I'm quite busy these days and don't have time to dig it, hence it is becoming a little unmanageable for me.
Did you have a chance to send the same patches for MediaTek? I appreciate that and I can help to test it on our platforms.
Ryder.
On Fri, Jun 23, 2017 at 05:13:16PM +0800, Ryder Lee wrote:
Sorry for late reply,
+Lorenzo
On Wed, 2017-06-21 at 18:04 +0800, Mark Brown wrote:
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host controller support).
Hi Lorenzo,
I picked up your changes and had some modifications like what you did for other platforms:
9f8e3a5 PCI: Add devm_pci_alloc_host_bridge() interface 35a1a84 PCI: Add pci_free_host_bridge() interface e33aafd PCI: Initialize bridge release function at bridge allocation
...and it looks Okay.
I have also noticed that you continue sending patches for other platforms but I have not yet had a look in detail. I'm quite busy these days and don't have time to dig it, hence it is becoming a little unmanageable for me.
If it is unmanageable you don't add yourself as a maintainer of that PCI host bridge driver, you know, we are all busy.
Your driver in the PCI tree as it stands contains already two bugs:
1) It leaks memory on the probe failure path 2) pci_fixup_irqs() is broken on configurations with multiple host bridges
And we keep copy'n'pasting that code.
Did you have a chance to send the same patches for MediaTek? I appreciate that and I can help to test it on our platforms.
No, how could I have sent them ? It is not upstream and it is a separate branch in the PCI tree. As I mentioned in another thread it is probably best to drop my pci_fixup_irqs() removal patches since it is impossible to work on them without a stable branch to apply them against, in the interim we keep adding PCI host bridges that use the wrong interfaces by copy'n'pasting code that I have been trying to remove.
I think the best solution is to repost my series when v4.13-rc1 appears and ask all new crop of host bridge drivers to rebase against it.
I won't be able to follow mailing lists till end of next week, which is bad timing.
Bjorn, is the plan above ok ? Please let me know how you want to proceed.
Thanks, Lorenzo
On Fri, 2017-06-23 at 10:43 +0100, Lorenzo Pieralisi wrote:
On Fri, Jun 23, 2017 at 05:13:16PM +0800, Ryder Lee wrote:
Sorry for late reply,
+Lorenzo
On Wed, 2017-06-21 at 18:04 +0800, Mark Brown wrote:
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host controller support).
Hi Lorenzo,
I picked up your changes and had some modifications like what you did for other platforms:
9f8e3a5 PCI: Add devm_pci_alloc_host_bridge() interface 35a1a84 PCI: Add pci_free_host_bridge() interface e33aafd PCI: Initialize bridge release function at bridge allocation
...and it looks Okay.
I have also noticed that you continue sending patches for other platforms but I have not yet had a look in detail. I'm quite busy these days and don't have time to dig it, hence it is becoming a little unmanageable for me.
If it is unmanageable you don't add yourself as a maintainer of that PCI host bridge driver, you know, we are all busy.
Your driver in the PCI tree as it stands contains already two bugs:
- It leaks memory on the probe failure path
- pci_fixup_irqs() is broken on configurations with multiple host bridges
And we keep copy'n'pasting that code.
Sure, I have already tested it, and I'll send a patch with your new methods :)
Did you have a chance to send the same patches for MediaTek? I appreciate that and I can help to test it on our platforms.
No, how could I have sent them ? It is not upstream and it is a separate branch in the PCI tree. As I mentioned in another thread it is probably best to drop my pci_fixup_irqs() removal patches since it is impossible to work on them without a stable branch to apply them against, in the interim we keep adding PCI host bridges that use the wrong interfaces by copy'n'pasting code that I have been trying to remove.
I think the best solution is to repost my series when v4.13-rc1 appears and ask all new crop of host bridge drivers to rebase against it.
I won't be able to follow mailing lists till end of next week, which is bad timing.
I meant I'm also not sure how to do it in separate branch. I didn't notice what you discussed in another thread. Sorry about that.
Bjorn, is the plan above ok ? Please let me know how you want to proceed.
Thanks, Lorenzo
Ryder
On Fri, Jun 23, 2017 at 06:22:13PM +0800, Ryder Lee wrote:
On Fri, 2017-06-23 at 10:43 +0100, Lorenzo Pieralisi wrote:
On Fri, Jun 23, 2017 at 05:13:16PM +0800, Ryder Lee wrote:
Sorry for late reply,
+Lorenzo
On Wed, 2017-06-21 at 18:04 +0800, Mark Brown wrote:
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host controller support).
Hi Lorenzo,
I picked up your changes and had some modifications like what you did for other platforms:
9f8e3a5 PCI: Add devm_pci_alloc_host_bridge() interface 35a1a84 PCI: Add pci_free_host_bridge() interface e33aafd PCI: Initialize bridge release function at bridge allocation
...and it looks Okay.
I have also noticed that you continue sending patches for other platforms but I have not yet had a look in detail. I'm quite busy these days and don't have time to dig it, hence it is becoming a little unmanageable for me.
If it is unmanageable you don't add yourself as a maintainer of that PCI host bridge driver, you know, we are all busy.
Your driver in the PCI tree as it stands contains already two bugs:
- It leaks memory on the probe failure path
- pci_fixup_irqs() is broken on configurations with multiple host bridges
And we keep copy'n'pasting that code.
Sure, I have already tested it, and I'll send a patch with your new methods :)
Thank you for testing it but please do not send anything before we decide what to do with my pci_fixup_irqs() removal series.
Did you have a chance to send the same patches for MediaTek? I appreciate that and I can help to test it on our platforms.
No, how could I have sent them ? It is not upstream and it is a separate branch in the PCI tree. As I mentioned in another thread it is probably best to drop my pci_fixup_irqs() removal patches since it is impossible to work on them without a stable branch to apply them against, in the interim we keep adding PCI host bridges that use the wrong interfaces by copy'n'pasting code that I have been trying to remove.
I think the best solution is to repost my series when v4.13-rc1 appears and ask all new crop of host bridge drivers to rebase against it.
I won't be able to follow mailing lists till end of next week, which is bad timing.
I meant I'm also not sure how to do it in separate branch. I didn't notice what you discussed in another thread. Sorry about that.
No worries, yes we need to understand how to sync the changes, as I said it is probably better for my series to be dropped, posted at v4.13-rc1, create a branch out of it and ask all PCI host bridges to be based against it, it is up to Bjorn to decide what's the least complicated way for him to sync all these changes.
Lorenzo
On Fri, Jun 23, 2017 at 10:43:56AM +0100, Lorenzo Pieralisi wrote:
On Fri, Jun 23, 2017 at 05:13:16PM +0800, Ryder Lee wrote:
Sorry for late reply,
+Lorenzo
On Wed, 2017-06-21 at 18:04 +0800, Mark Brown wrote:
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
arm-allmodconfig ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit declaration of function 'pci_register_host_bridge' [-Werror=implicit-function-declaration]
caused by eaf3023b0498a (PCI: mediatek: Add MediaTek PCIe host controller support).
Hi Lorenzo,
I picked up your changes and had some modifications like what you did for other platforms:
9f8e3a5 PCI: Add devm_pci_alloc_host_bridge() interface 35a1a84 PCI: Add pci_free_host_bridge() interface e33aafd PCI: Initialize bridge release function at bridge allocation
...and it looks Okay.
I have also noticed that you continue sending patches for other platforms but I have not yet had a look in detail. I'm quite busy these days and don't have time to dig it, hence it is becoming a little unmanageable for me.
If it is unmanageable you don't add yourself as a maintainer of that PCI host bridge driver, you know, we are all busy.
Your driver in the PCI tree as it stands contains already two bugs:
- It leaks memory on the probe failure path
- pci_fixup_irqs() is broken on configurations with multiple host bridges
And we keep copy'n'pasting that code.
Did you have a chance to send the same patches for MediaTek? I appreciate that and I can help to test it on our platforms.
No, how could I have sent them ? It is not upstream and it is a separate branch in the PCI tree. As I mentioned in another thread it is probably best to drop my pci_fixup_irqs() removal patches since it is impossible to work on them without a stable branch to apply them against, in the interim we keep adding PCI host bridges that use the wrong interfaces by copy'n'pasting code that I have been trying to remove.
I think the best solution is to repost my series when v4.13-rc1 appears and ask all new crop of host bridge drivers to rebase against it.
I won't be able to follow mailing lists till end of next week, which is bad timing.
Bjorn, is the plan above ok ? Please let me know how you want to proceed.
Sorry, I was on vacation myself most of last week, and you're unavailable most of this week, but I'd still like to try to get this into v4.13.
We may not get every host tested, but I'm not sure that will happen even if we wait for the next cycle. If we trip over something it will likely be something small or for a relatively rare platform, so we can fix it up after the fact.
I haven't looked at everything yet, but my plan is to try to incorporate the fixes people have posted and keep pushing forward. If that turns out not to work, I'll drop the pci_fixup_irqs() series, but I'll at least give it a try.
Bjorn
On Wed, Jun 21, 2017 at 10:56:07AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig with:
../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token ../include/linux/qed/qede_rdma.h:85:1: error: expected identifier or '(' before '{' token
caused by bbfcd1e8e1677b (qed*: Set rdma generic functions prefix), the stub for !QED_RDMA just has a syntax error.
kernel-build-reports@lists.linaro.org
-
Bjorn Helgaas -
Build bot for Mark Brown -
Lorenzo Pieralisi -
Mark Brown
-
Ryder Lee