From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, tony@atomide.com,
linux@arm.linux.org.uk, eduardo.valentin@ti.com
Subject: Re: [RFC PATCH v2 0/2] ARM: update cpuinfo to print SoC model name
Date: Wed, 30 Jan 2013 11:30:56 +0530 [thread overview]
Message-ID: <5108B718.3050507@ti.com> (raw)
In-Reply-To: <1359506337-21619-1-git-send-email-ruslan.bilovol@ti.com>
On Wednesday 30 January 2013 06:08 AM, Ruslan Bilovol wrote:
> The following patches update cpuinfo to print SoC
> model name for ARM.
> The first patch exactly makes needed changes for ARM
> architecture and adds a common approach to show SoC name.
> Second patch uses this approach for OMAP4 SoCs (as live
> example).
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck (had stuck
> on review) so this functionality is still not
> in the kernel yet.
> In this patch series the update to cpuinfo is very
> short (10 lines) and easy.
>
> Comments are welcome as usual
>
As most of the people already commented, your purpose
behind the series isn't clear so please give examples
where and why you need device type information from
user-space.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/2] ARM: update cpuinfo to print SoC model name
Date: Wed, 30 Jan 2013 11:30:56 +0530 [thread overview]
Message-ID: <5108B718.3050507@ti.com> (raw)
In-Reply-To: <1359506337-21619-1-git-send-email-ruslan.bilovol@ti.com>
On Wednesday 30 January 2013 06:08 AM, Ruslan Bilovol wrote:
> The following patches update cpuinfo to print SoC
> model name for ARM.
> The first patch exactly makes needed changes for ARM
> architecture and adds a common approach to show SoC name.
> Second patch uses this approach for OMAP4 SoCs (as live
> example).
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck (had stuck
> on review) so this functionality is still not
> in the kernel yet.
> In this patch series the update to cpuinfo is very
> short (10 lines) and easy.
>
> Comments are welcome as usual
>
As most of the people already commented, your purpose
behind the series isn't clear so please give examples
where and why you need device type information from
user-space.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tony@atomide.com>, <linux@arm.linux.org.uk>,
<eduardo.valentin@ti.com>
Subject: Re: [RFC PATCH v2 0/2] ARM: update cpuinfo to print SoC model name
Date: Wed, 30 Jan 2013 11:30:56 +0530 [thread overview]
Message-ID: <5108B718.3050507@ti.com> (raw)
In-Reply-To: <1359506337-21619-1-git-send-email-ruslan.bilovol@ti.com>
On Wednesday 30 January 2013 06:08 AM, Ruslan Bilovol wrote:
> The following patches update cpuinfo to print SoC
> model name for ARM.
> The first patch exactly makes needed changes for ARM
> architecture and adds a common approach to show SoC name.
> Second patch uses this approach for OMAP4 SoCs (as live
> example).
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck (had stuck
> on review) so this functionality is still not
> in the kernel yet.
> In this patch series the update to cpuinfo is very
> short (10 lines) and easy.
>
> Comments are welcome as usual
>
As most of the people already commented, your purpose
behind the series isn't clear so please give examples
where and why you need device type information from
user-space.
Regards,
Santosh
next prev parent reply other threads:[~2013-01-30 5:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 0:38 [RFC PATCH v2 0/2] ARM: update cpuinfo to print SoC model name Ruslan Bilovol
2013-01-30 0:38 ` Ruslan Bilovol
2013-01-30 0:38 ` [RFC PATCH v2 1/2] ARM: kernel: " Ruslan Bilovol
2013-01-30 0:38 ` Ruslan Bilovol
2013-01-30 5:48 ` Nishanth Menon
2013-01-30 5:48 ` Nishanth Menon
2013-01-30 0:38 ` [RFC PATCH v2 2/2] ARM: OMAP4: setup SoC model name during ID initialisation Ruslan Bilovol
2013-01-30 0:38 ` Ruslan Bilovol
2013-01-30 6:00 ` Santosh Shilimkar [this message]
2013-01-30 6:00 ` [RFC PATCH v2 0/2] ARM: update cpuinfo to print SoC model name Santosh Shilimkar
2013-01-30 6:00 ` Santosh Shilimkar
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=5108B718.3050507@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=eduardo.valentin@ti.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 \
--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.