linux-kernel - Re: Renaming ARM

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-prev] [day] [month] [year] [list]

Date:	Mon, 23 Mar 2015 17:06:28 +0100
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	"Suzuki K. Poulose" <Suzuki.Poulose@....com>
Cc:	"linux@....linux.org.uk" <linux@....linux.org.uk>,
	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 Mon, Mar 23, 2015 at 5:04 PM, Suzuki K. Poulose
<Suzuki.Poulose@....com> wrote:
> On 23/03/15 15:17, Suzuki K. Poulose wrote:
>>
>> 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
>
> Somehow, the link above doesn't link my response to the thread.
> Please find it below.
>
>         https://lkml.org/lkml/2015/3/23/484

Thank you for the answer and the explanation.

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/