From: Tony Lindgren <tony@atomide.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: OMAP2+: SoC name and revision unification
Date: Tue, 5 Feb 2013 15:56:26 -0800 [thread overview]
Message-ID: <20130205235626.GS25185@atomide.com> (raw)
In-Reply-To: <1359660284-5225-2-git-send-email-ruslan.bilovol@ti.com>
* Ruslan Bilovol <ruslan.bilovol@ti.com> [130131 11:28]:
> This is a long story where for each new generation of
> OMAP we used different approaches for creating
> strings for SoCs names and revisions that this patch
> fixes. It makes future exporting of this information
> to SoC infrastructure easier.
Maybe use name soc_name and soc_rev instead and make
cpu_name and cpu_rev local to the functions?
That would reduce some churn here.
Also this does not apply to my omap-for-v3.9/soc
branch. Care to update this (and possibly the second one)
against that?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: SoC name and revision unification
Date: Tue, 5 Feb 2013 15:56:26 -0800 [thread overview]
Message-ID: <20130205235626.GS25185@atomide.com> (raw)
In-Reply-To: <1359660284-5225-2-git-send-email-ruslan.bilovol@ti.com>
* Ruslan Bilovol <ruslan.bilovol@ti.com> [130131 11:28]:
> This is a long story where for each new generation of
> OMAP we used different approaches for creating
> strings for SoCs names and revisions that this patch
> fixes. It makes future exporting of this information
> to SoC infrastructure easier.
Maybe use name soc_name and soc_rev instead and make
cpu_name and cpu_rev local to the functions?
That would reduce some churn here.
Also this does not apply to my omap-for-v3.9/soc
branch. Care to update this (and possibly the second one)
against that?
Regards,
Tony
next prev parent reply other threads:[~2013-02-05 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 19:24 [PATCH 0/2] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure Ruslan Bilovol
2013-01-31 19:24 ` Ruslan Bilovol
2013-01-31 19:24 ` [PATCH 1/2] ARM: OMAP2+: SoC name and revision unification Ruslan Bilovol
2013-01-31 19:24 ` Ruslan Bilovol
2013-02-05 23:56 ` Tony Lindgren [this message]
2013-02-05 23:56 ` Tony Lindgren
2013-02-06 15:11 ` Ruslan Bilovol
2013-02-06 15:11 ` Ruslan Bilovol
2013-01-31 19:24 ` [PATCH 2/2] ARM: OMAP2+: Export SoC information to userspace Ruslan Bilovol
2013-01-31 19:24 ` Ruslan Bilovol
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=20130205235626.GS25185@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ruslan.bilovol@ti.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.