From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>
Cc: Sudeep Holla <Sudeep.Holla@arm.com>,
"nicolas.pitre@linaro.org" <nicolas.pitre@linaro.org>,
Punit Agrawal <Punit.Agrawal@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Bolle <pebolle@tiscali.nl>,
Andreas Ruprecht <rupran@einserver.de>,
hengelein Stefan <stefan.hengelein@fau.de>
Subject: Re: Renaming ARM_CCI
Date: Mon, 23 Mar 2015 16:04:00 +0000 [thread overview]
Message-ID: <55103970.2060907@arm.com> (raw)
In-Reply-To: <55102E82.1080404@arm.com>
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
Suzuki
next prev parent reply other threads:[~2015-03-23 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 15:10 Renaming ARM_CCI Valentin Rothberg
2015-03-23 15:17 ` Suzuki K. Poulose
2015-03-23 16:04 ` Suzuki K. Poulose [this message]
2015-03-23 16:06 ` Valentin Rothberg
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=55103970.2060907@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Punit.Agrawal@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=Will.Deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.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