From: Samuel Ortiz <sameo@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86, mrst: add platform support for MSIC MFD driver
Date: Thu, 20 Oct 2011 18:47:43 +0200 [thread overview]
Message-ID: <20111020164743.GA3871@sortiz-mobl> (raw)
In-Reply-To: <1318930882-10017-1-git-send-email-mika.westerberg@linux.intel.com>
Hi Mika,
On Tue, Oct 18, 2011 at 12:41:22PM +0300, Mika Westerberg wrote:
> The MSIC MFD driver creates platform devices for MSIC device drivers so we
> don't need to create them in platform code anymore.
>
> This patch adds a new runtime check which determines whether we are running
> on a Medfield platform and enables the MSIC MFD driver accordingly.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
I applied this new version, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-10-20 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 13:06 [PATCH 0/3] Intel MSIC MFD driver for Medfield platform Mika Westerberg
2011-09-07 13:06 ` [PATCH 1/3] mfd: add Intel MSIC driver Mika Westerberg
2011-09-20 17:17 ` Samuel Ortiz
2011-09-21 8:07 ` Mika Westerberg
2011-09-21 10:44 ` Samuel Ortiz
2011-09-21 11:12 ` Mika Westerberg
2011-09-07 13:06 ` [PATCH 2/3] x86, mrst: Some drivers need to known when an SCU is available Mika Westerberg
2011-09-07 13:06 ` [PATCH 3/3] x86, mrst: add platform support for MSIC MFD driver Mika Westerberg
2011-10-14 7:59 ` Mika Westerberg
2011-10-18 9:13 ` Samuel Ortiz
2011-10-18 9:41 ` [PATCH v2] " Mika Westerberg
2011-10-20 16:47 ` Samuel Ortiz [this message]
2011-09-19 7:34 ` [PATCH 0/3] Intel MSIC MFD driver for Medfield platform Mika Westerberg
2011-09-19 8:05 ` Samuel Ortiz
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=20111020164743.GA3871@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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).