From: Shinya Kuribayashi <shinya.kuribayashi.px-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
To: Alan Cox <alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [CORRECTED] I2C driver supporting Moorestown and Medfield platform
Date: Tue, 10 Aug 2010 08:58:01 +0900 [thread overview]
Message-ID: <4C609609.6070307@renesas.com> (raw)
In-Reply-To: <20100809120743.05e22ef4-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
On 8/9/2010 8:07 PM, Alan Cox wrote:
> There are various little differences along with the PCI, power
> management, timing and configuration side. I've also looked at the two
I'm interested in those little diffs.
> side by side and agreed with the original Intel authors that it seemed
> best to keep it as two drivers. Otherwise you drag a lot of PCI and PCI
> pm logic into a simpler driver that is used on non PCI platforms.
Got it, thanks. I'll have a look at the differences, first.
--
Shinya Kuribayashi
Renesas Electronics
next prev parent reply other threads:[~2010-08-09 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 14:34 [CORRECTED] I2C driver supporting Moorestown and Medfield platform Alan Cox
[not found] ` <20100803143431.23655.31975.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-08-09 5:52 ` Shinya Kuribayashi
[not found] ` <4C5F97AC.1020509-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2010-08-09 11:07 ` Alan Cox
[not found] ` <20100809120743.05e22ef4-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2010-08-09 23:58 ` Shinya Kuribayashi [this message]
2010-08-09 10:59 ` Ben Dooks
[not found] ` <4C5FDFA9.60703-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
2010-08-09 12:23 ` Alan Cox
[not found] ` <20100809132345.44fdbaea-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2010-08-31 22:44 ` Ben Dooks
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=4C609609.6070307@renesas.com \
--to=shinya.kuribayashi.px-zm6kxycvzfbbdgjk7y7tuq@public.gmane.org \
--cc=alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.