From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP: DRA7: Make use of omap_revision information for soc_is* calls
Date: Fri, 19 Feb 2016 10:15:14 -0800 [thread overview]
Message-ID: <20160219181514.GK21202@atomide.com> (raw)
In-Reply-To: <1455706123-26497-1-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [160217 02:49]:
> Currently of_machine_is_compatible is used to detect the soc which
> employs string comparison operations. We already have all the required
> information in the omap_revision. Hence make use of the same like
> the previous OMAPs and avoid costly string comparisons.
Looks good to me thanks. Applying into omap-for-v4.6/soc.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: DRA7: Make use of omap_revision information for soc_is* calls
Date: Fri, 19 Feb 2016 10:15:14 -0800 [thread overview]
Message-ID: <20160219181514.GK21202@atomide.com> (raw)
In-Reply-To: <1455706123-26497-1-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [160217 02:49]:
> Currently of_machine_is_compatible is used to detect the soc which
> employs string comparison operations. We already have all the required
> information in the omap_revision. Hence make use of the same like
> the previous OMAPs and avoid costly string comparisons.
Looks good to me thanks. Applying into omap-for-v4.6/soc.
Tony
next prev parent reply other threads:[~2016-02-19 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:48 [PATCH] ARM: OMAP: DRA7: Make use of omap_revision information for soc_is* calls Keerthy
2016-02-17 10:48 ` Keerthy
2016-02-19 18:15 ` Tony Lindgren [this message]
2016-02-19 18:15 ` Tony Lindgren
2016-02-22 3:27 ` Keerthy
2016-02-22 3:27 ` 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=20160219181514.GK21202@atomide.com \
--to=tony@atomide.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.