linux-kernel - powerpc: CONFIG_PPC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150410115410.GA21121@station.rsr.lip6.fr>
Date:	Fri, 10 Apr 2015 13:54:10 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	mpe@...erman.id.au
Cc:	benh@...nel.crashing.org, jk@...abs.org, pebolle@...cali.nl,
	rupran@...server.de, stefan.hengelein@....de,
	cbe-oss-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	linuxppc-dev@...ts.ozlabs.org, paulus@...ba.org
Subject: powerpc: CONFIG_PPC_CELLEB leftovers

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/