Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755478AbbDJMBe (ORCPT ); Fri, 10 Apr 2015 08:01:34 -0400 Received: from mail-wi0-f175.google.com ([209.85.212.175]:35303 "EHLO mail-wi0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751431AbbDJMBc (ORCPT ); Fri, 10 Apr 2015 08:01:32 -0400 Date: Fri, 10 Apr 2015 13:54:10 +0200 From: Valentin Rothberg To: mpe@ellerman.id.au Cc: benh@kernel.crashing.org, jk@ozlabs.org, pebolle@tiscali.nl, rupran@einserver.de, stefan.hengelein@fau.de, cbe-oss-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, paulus@samba.org Subject: powerpc: CONFIG_PPC_CELLEB leftovers Message-ID: <20150410115410.GA21121@station.rsr.lip6.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1124 Lines: 24 Hi Michael, your commit bf4981a00636 ("powerpc: Remove the celleb support") in today's Linux next tree removes the Kconfig option PPC_CELLEB. It looks like there are some leftovers in Kconfig dependencies on this option which avoid to properly set others (see list below). Is there a patch queued somewhere to fix the issue? 0 drivers/ata/Kconfig 734 depends on PCI && PPC_CELLEB 1 drivers/ide/Kconfig 648 depends on PPC_CELLEB 2 drivers/net/ethernet/toshiba/Kconfig 8 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB || MIPS) || PPC_PS3 3 drivers/net/ethernet/toshiba/Kconfig 45 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 4 drivers/tty/hvc/Kconfig 47 depends on PPC_CELLEB I detected the issue with ./scripts/checkkonfigsymbols.py by diffing today's and yesterday's Linux next trees. Kind regards, Valentin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/