From: Michael Ellerman <mpe@ellerman.id.au>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: cbe-oss-dev@lists.ozlabs.org, pebolle@tiscali.nl,
linux-kernel@vger.kernel.org, paulus@samba.org, jk@ozlabs.org,
rupran@einserver.de, linuxppc-dev@lists.ozlabs.org,
stefan.hengelein@fau.de
Subject: Re: powerpc: CONFIG_PPC_CELLEB leftovers
Date: Sat, 11 Apr 2015 20:42:12 +1000 [thread overview]
Message-ID: <1428748932.1552.1.camel@ellerman.id.au> (raw)
In-Reply-To: <20150410115410.GA21121@station.rsr.lip6.fr>
On Fri, 2015-04-10 at 13:54 +0200, Valentin Rothberg wrote:
> Hi Michael,
Hi Valentin,
> 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?
There are not yet patches to fix those.
> 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.
Thanks.
I'll try and get patches for those done this week, but no promises.
cheers
prev parent reply other threads:[~2015-04-11 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 11:54 powerpc: CONFIG_PPC_CELLEB leftovers Valentin Rothberg
2015-04-11 10:42 ` Michael Ellerman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428748932.1552.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=jk@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=pebolle@tiscali.nl \
--cc=rupran@einserver.de \
--cc=stefan.hengelein@fau.de \
--cc=valentinrothberg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).