From: Andrew Morton <akpm@linux-foundation.org>
To: viresh kumar <viresh.linux@gmail.com>
Cc: salvatore.dedominicis@st.com, bhavna.yadav@st.com,
rajeev-dlh.kumar@st.com, Viresh Kumar <viresh.kumar@st.com>,
pratyush.anand@st.com, shiraz.hashim@st.com, deepak.sikri@st.com,
mirko.gardi@st.com, vipulkumar.samar@st.com, rui.zhang@intel.com,
len.brown@intel.com, armando.visconti@st.com, amit.virdi@st.com,
vincenzo.frascino@st.com, vipin.kumar@st.com,
linux-kernel@vger.kernel.org, bhupesh.sharma@st.com
Subject: Re: [PATCH] thermal: Add support for thermal sensor present on SPEAr13xx machines
Date: Mon, 27 Feb 2012 14:49:00 -0800 [thread overview]
Message-ID: <20120227144900.e7a9d972.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAOh2x=kszwxhwKqwKN37Yd_KRKG5DwC_5zXXevsLpUJmJsZV0w@mail.gmail.com>
On Fri, 24 Feb 2012 19:30:54 -0800
viresh kumar <viresh.linux@gmail.com> wrote:
> On Feb 25, 2012 1:32 AM, "Andrew Morton" <akpm@linux-foundation.org> wrote:
> >
>
> > The driver can be compiled for all architectures which support
> > CONFIG_THERMAL. This includes x86_64. Was that intended?
> >
>
> No.
>
> > I don't think it's necessarily a bad thing:
>
> Ya we thought about removing spear_* from the driver. But the hardware
> looked a bit proprietary.
I don't really understand this reply. Does it mean that you will be
updating the Kconfig logic?
prev parent reply other threads:[~2012-02-27 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 7:27 [PATCH] thermal: Add support for thermal sensor present on SPEAr13xx machines Viresh Kumar
2012-02-24 20:02 ` Andrew Morton
[not found] ` <CAOh2x=kszwxhwKqwKN37Yd_KRKG5DwC_5zXXevsLpUJmJsZV0w@mail.gmail.com>
2012-02-27 22:49 ` Andrew Morton [this message]
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=20120227144900.e7a9d972.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amit.virdi@st.com \
--cc=armando.visconti@st.com \
--cc=bhavna.yadav@st.com \
--cc=bhupesh.sharma@st.com \
--cc=deepak.sikri@st.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirko.gardi@st.com \
--cc=pratyush.anand@st.com \
--cc=rajeev-dlh.kumar@st.com \
--cc=rui.zhang@intel.com \
--cc=salvatore.dedominicis@st.com \
--cc=shiraz.hashim@st.com \
--cc=vincenzo.frascino@st.com \
--cc=vipin.kumar@st.com \
--cc=vipulkumar.samar@st.com \
--cc=viresh.kumar@st.com \
--cc=viresh.linux@gmail.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;
as well as URLs for NNTP newsgroup(s).