From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: DRA752: add detection of SoC information
Date: Mon, 19 May 2014 17:34:34 -0700 [thread overview]
Message-ID: <20140520003433.GB15793@atomide.com> (raw)
In-Reply-To: <1400513231-25092-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [140519 08:28]:
> Currently the files in /sys/devices/soc0/ show no information about
> DRA7. Few userspace programs do depend on this information to make SoC
> specific support. So update logic to detect the relevant information and
> provide to userspace.
Thanks applying into omap-for-v3.16/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: DRA752: add detection of SoC information
Date: Mon, 19 May 2014 17:34:34 -0700 [thread overview]
Message-ID: <20140520003433.GB15793@atomide.com> (raw)
In-Reply-To: <1400513231-25092-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [140519 08:28]:
> Currently the files in /sys/devices/soc0/ show no information about
> DRA7. Few userspace programs do depend on this information to make SoC
> specific support. So update logic to detect the relevant information and
> provide to userspace.
Thanks applying into omap-for-v3.16/soc.
Tony
next prev parent reply other threads:[~2014-05-20 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 15:27 [PATCH] ARM: DRA752: add detection of SoC information Nishanth Menon
2014-05-19 15:27 ` Nishanth Menon
2014-05-20 0:34 ` Tony Lindgren [this message]
2014-05-20 0:34 ` Tony Lindgren
2014-05-20 6:04 ` Rajendra Nayak
2014-05-20 6:04 ` Rajendra Nayak
2014-05-20 11:20 ` Nishanth Menon
2014-05-20 11:20 ` Nishanth Menon
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=20140520003433.GB15793@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=rnayak@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.