linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Bill Brown <bill.e.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c: Adding support for Intel iSMT SMBus 2.0 host controller
Date: Fri, 3 Aug 2012 08:33:42 +0200	[thread overview]
Message-ID: <20120803083342.76f0df3b@endymion.delvare> (raw)
In-Reply-To: <1343954343.24204.5.camel-ttzMDwopN+0VpfeQ83dqLK2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>

Hi Bill,

On Thu, 02 Aug 2012 17:39:03 -0700, Bill Brown wrote:
> On Mon, 2012-07-30 at 14:23 -0700, Bill Brown wrote:
> > The iSMT (Intel SMBus Message Transport) supports multi-master I2C/SMBus,
> > as well as IPMI.  It's operation is DMA-based and utilizes descriptors to
> > initiate transactions on the bus.
> > 
> > The iSMT hardware can act as both a master and a target, although this
> > driver only supports being a master.
> > 
> > Signed-off-by: Bill Brown <bill.e.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> I haven't seen any activity on this yet...good to go, or has anyone had
> a chance to review it yet?  I'd like to get it into the 3.6 kernel if
> possible.

Summer time is when when people take vacation, this increases review
delays.

I'm afraid it's too late for 3.6, rc1 is already out. In order to get a
patch in a kernel version, you must have it in linux-next before the
merge window opens.

-- 
Jean Delvare

      parent reply	other threads:[~2012-08-03  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 21:23 [PATCH] i2c: Adding support for Intel iSMT SMBus 2.0 host controller Bill Brown
     [not found] ` <1343683421-12504-1-git-send-email-bill.e.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-08-03  0:39   ` Bill Brown
     [not found]     ` <1343954343.24204.5.camel-ttzMDwopN+0VpfeQ83dqLK2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>
2012-08-03  6:33       ` Jean Delvare [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=20120803083342.76f0df3b@endymion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=bill.e.brown-ral2JQCrhuEAvxtiuMwx3w@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 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).