diff options
author | Michael Ellerman <mpe@ellerman.id.au> | 2019-02-07 13:43:26 +1100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-04-05 22:34:32 +0200 |
commit | a332ad5f006fee3ff35883d38424a164da02a73f (patch) | |
tree | 8411d5a82920d3147f23425172d5b17c7f4d926d /arch/powerpc/platforms/cell/ras.h | |
parent | 4974ca47f15c7320208ae4ac99da83edf4385c4a (diff) | |
download | talos-obmc-linux-a332ad5f006fee3ff35883d38424a164da02a73f.tar.gz talos-obmc-linux-a332ad5f006fee3ff35883d38424a164da02a73f.zip |
powerpc/44x: Force PCI on for CURRITUCK
[ Upstream commit aa7150ba378650d0e9d84b8e4d805946965a5926 ]
The recent rework of PCI kconfig symbols exposed an existing bug in
the CURRITUCK kconfig logic.
It selects PPC4xx_PCI_EXPRESS which depends on PCI, but PCI is user
selectable and might be disabled, leading to a warning:
WARNING: unmet direct dependencies detected for PPC4xx_PCI_EXPRESS
Depends on [n]: PCI [=n] && 4xx [=y]
Selected by [y]:
- CURRITUCK [=y] && PPC_47x [=y]
Prior to commit eb01d42a7778 ("PCI: consolidate PCI config entry in
drivers/pci") PCI was enabled by default for currituck_defconfig so we
didn't see the warning. The bad logic was still there, it just
required someone disabling PCI in their .config to hit it.
Fix it by forcing PCI on for CURRITUCK, which seems was always the
expectation anyway.
Fixes: eb01d42a7778 ("PCI: consolidate PCI config entry in drivers/pci")
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/powerpc/platforms/cell/ras.h')
0 files changed, 0 insertions, 0 deletions