linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Richard Rojfors
	<richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH 0/1] misc: Add Tunnel creek In-Vehicle I2C loader driver
Date: Fri, 15 Oct 2010 13:30:17 +0100	[thread overview]
Message-ID: <20101015123017.GL14782@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101015142130.1cf14629-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>

On Fri, Oct 15, 2010 at 02:21:30PM +0200, Jean Delvare wrote:

> My point still holds, regardless of what exactly Intel has in the
> works: if board config is now needed on some x86 systems, then support
> for it should be added in the same way other architectures did before.
> I can't see any reason why x86 would be different.

Oh, absolutely - I'm just saying that the existing Intel work isn't
useful for this as it's tied to Moorestown and SFI.

      parent reply	other threads:[~2010-10-15 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 14:41 [PATCH 0/1] misc: Add Tunnel creek In-Vehicle I2C loader driver Richard Röjfors
2010-09-29  8:38 ` Richard Röjfors
     [not found]   ` <4CA2FB10.2020605-gfIc91nka+FZroRs9YW3xA@public.gmane.org>
2010-10-15  8:49     ` Jean Delvare
     [not found]       ` <20101015104902.1047c978-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-10-15 12:10         ` Mark Brown
     [not found]           ` <20101015121042.GA27369-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2010-10-15 12:21             ` Jean Delvare
     [not found]               ` <20101015142130.1cf14629-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-10-15 12:30                 ` Mark Brown [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=20101015123017.GL14782@rakim.wolfsonmicro.main \
    --to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=richard.rojfors-gfIc91nka+FZroRs9YW3xA@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 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).