[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55102E82.1080404@arm.com>
Date: Mon, 23 Mar 2015 15:17:22 +0000
From: "Suzuki K. Poulose" <Suzuki.Poulose@....com>
To: Valentin Rothberg <valentinrothberg@...il.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>
CC: Sudeep Holla <Sudeep.Holla@....com>,
"nicolas.pitre@...aro.org" <nicolas.pitre@...aro.org>,
Punit Agrawal <Punit.Agrawal@....com>,
Will Deacon <Will.Deacon@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Paul Bolle <pebolle@...cali.nl>,
Andreas Ruprecht <rupran@...server.de>,
hengelein Stefan <stefan.hengelein@....de>
Subject: Re: Renaming ARM_CCI
On 23/03/15 15:10, Valentin Rothberg wrote:
> Hi Suzuki,
>
> your commit c9966c98697a ("arm-cci: Split the code for PMU vs driver
> support") renames the Kconfig option ARM_CCI to ARM_CCI400_PORT_CTRL.
> However, the commit does not rename all references on ARM_CCI:
>
It renames, but still, leaves the ARM_CCI to build the arm-cci.o, which
is in the original commit.
> drivers/bus/Kconfig:29: select ARM_CCI
> drivers/bus/Makefile:6:obj-$(CONFIG_ARM_CCI) += arm-cci.o
> include/linux/arm-cci.h:31:#ifdef CONFIG_ARM_CCI
>
> Is this intentional or is there a patch scheduled somewhere to fix this issue?
Yes, it is. This problem was introduced due to a conflict in the linux-next.
See :
https://lkml.org/lkml/2015/3/22/240
Cheers
Suzuki
--
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/
Powered by blists - more mailing lists