From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Eduardo Valentin <eduardo.valentin@nokia.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Linux-OMAP <linux-omap@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
ext Tony Lindgren <tony@atomide.com>,
ext Kevin Hilman <khilman@deeprootsystems.com>,
Peter De-Schrijver <Peter.De-Schrijver@nokia.com>,
santosh.shilimkar@ti.com, Ambresh <a0393775@ti.com>,
felipe.balbi@nokia.com
Subject: Re: [PATCHv4 3/4] mach-omap1: export omap1 info under /proc/socinfo
Date: Mon, 10 May 2010 11:52:00 +0100 [thread overview]
Message-ID: <20100510105200.GA14337@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1273487857-32281-4-git-send-email-eduardo.valentin@nokia.com>
On Mon, May 10, 2010 at 01:37:36PM +0300, Eduardo Valentin wrote:
> From: Eduardo Valentin <eduardo.valentin@nokia.com>
>
> Report OMAP name and rev under /proc/socinfo node.
I think this needs to be combined with the previous patch. The previous
patch enables the socinfo file, which means with patch 2 applied but not
patch 3, OMAP1 breaks.
next prev parent reply other threads:[~2010-05-10 10:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 10:37 [PATCHv4 0/4] Introduce the /proc/socinfo and use it to export OMAP data Eduardo Valentin
2010-05-10 10:37 ` [PATCHv4 1/4] procfs: Introduce socinfo under /proc Eduardo Valentin
2010-05-10 11:13 ` Paul Mundt
2010-05-10 12:35 ` Eduardo Valentin
2010-05-10 12:39 ` Paul Mundt
2010-05-10 12:55 ` Eduardo Valentin
2010-05-11 3:14 ` Paul Mundt
2010-05-11 6:21 ` Russell King - ARM Linux
2010-05-10 12:54 ` Felipe Balbi
2010-05-10 13:08 ` Eduardo Valentin
2010-05-10 18:15 ` Felipe Balbi
2010-05-10 14:22 ` Eduardo Valentin
2010-05-11 3:11 ` Paul Mundt
2010-05-10 10:37 ` [PATCHv4 2/4] mach-omap2: export omap2 info under /proc/socinfo Eduardo Valentin
2010-05-10 10:37 ` [PATCHv4 3/4] mach-omap1: export omap1 " Eduardo Valentin
2010-05-10 10:52 ` Russell King - ARM Linux [this message]
2010-05-10 12:13 ` Eduardo Valentin
2010-05-10 10:37 ` [PATCHv4 4/4] OMAP3: export chip IDCODE, Production ID and Die ID Eduardo Valentin
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=20100510105200.GA14337@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Peter.De-Schrijver@nokia.com \
--cc=a0393775@ti.com \
--cc=akpm@linux-foundation.org \
--cc=eduardo.valentin@nokia.com \
--cc=felipe.balbi@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox