All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keerthy <a0393675@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Keerthy <j-keerthy@ti.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFT PATCH] ARM: OMAP: Change all cpu_is_* occurences to soc_is_*
Date: Tue, 25 Aug 2015 11:12:48 +0530	[thread overview]
Message-ID: <55DC0058.7080101@ti.com> (raw)
In-Reply-To: <20150824212442.GI7576@n2100.arm.linux.org.uk>



On Tuesday 25 August 2015 02:54 AM, Russell King - ARM Linux wrote:
> On Tue, Aug 18, 2015 at 03:40:01PM +0530, Keerthy wrote:
>> Currently apart from dra7, omap5 and amx3 all the other SoCs
>> are identified using cpu_is_* functions which is not right since
>> they are all SoCs(System on Chips). Hence changing the SoC
>> identificätion code to use soc_is instead of cpu_is and keeping
>             ^
> typo

I will correct and send a v2.

>
>> defines for cpu_is where needed. This allows us to replace the
>> rest of cpu_is usage along with other fixes as needed.
>
> Good to see this change to a more sensible naming of these, despite
> the obvious churn.
>
> Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>

Thanks Russel. I will fix the above typo and add your Ack in the next 
version.

>

WARNING: multiple messages have this Message-ID (diff)
From: Keerthy <a0393675@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Keerthy <j-keerthy@ti.com>
Cc: <tony@atomide.com>, <linux-omap@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFT PATCH] ARM: OMAP: Change all cpu_is_* occurences to soc_is_*
Date: Tue, 25 Aug 2015 11:12:48 +0530	[thread overview]
Message-ID: <55DC0058.7080101@ti.com> (raw)
In-Reply-To: <20150824212442.GI7576@n2100.arm.linux.org.uk>



On Tuesday 25 August 2015 02:54 AM, Russell King - ARM Linux wrote:
> On Tue, Aug 18, 2015 at 03:40:01PM +0530, Keerthy wrote:
>> Currently apart from dra7, omap5 and amx3 all the other SoCs
>> are identified using cpu_is_* functions which is not right since
>> they are all SoCs(System on Chips). Hence changing the SoC
>> identificätion code to use soc_is instead of cpu_is and keeping
>             ^
> typo

I will correct and send a v2.

>
>> defines for cpu_is where needed. This allows us to replace the
>> rest of cpu_is usage along with other fixes as needed.
>
> Good to see this change to a more sensible naming of these, despite
> the obvious churn.
>
> Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>

Thanks Russel. I will fix the above typo and add your Ack in the next 
version.

>

  reply	other threads:[~2015-08-25  5:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 10:10 [RFT PATCH] ARM: OMAP: Change all cpu_is_* occurences to soc_is_* Keerthy
2015-08-18 10:10 ` Keerthy
2015-08-18 11:54 ` Keerthy
2015-08-18 11:54   ` Keerthy
2015-08-24  5:52   ` Keerthy
2015-08-24  5:52     ` Keerthy
2015-08-24 21:24 ` Russell King - ARM Linux
2015-08-25  5:42   ` Keerthy [this message]
2015-08-25  5:42     ` Keerthy

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=55DC0058.7080101@ti.com \
    --to=a0393675@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.