All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: sensors@Stimpy.netroedge.com, linuxppc-embedded@lists.linuxppc.org
Subject: [PATCH] PPC4xx IIC driver: 0-length transactions bit-banging
Date: Thu, 19 May 2005 06:25:05 +0000	[thread overview]
Message-ID: <20040708230713.GF20431@kroah.com> (raw)
In-Reply-To: <20040622185116.GA4146@gate.ebshome.net>

On Tue, Jun 22, 2004 at 11:51:16AM -0700, Eugene Surovegin wrote:
> Greg,
> 
> IBM PPC 4xx i2c controller doesn't support 0-length transactions (e.g. used by 
> SMBUS_QUICK). This patch implements bit-banging emulation for such requests and 
> removes temporary kludge added earlier.
> 
> Signed-off-by: Eugene Surovegin <ebs@ebshome.net>
> 
> Please, apply.

Applied, thanks.

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: sensors@Stimpy.netroedge.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] PPC4xx IIC driver: 0-length transactions bit-banging implementation
Date: Thu, 8 Jul 2004 16:07:13 -0700	[thread overview]
Message-ID: <20040708230713.GF20431@kroah.com> (raw)
In-Reply-To: <20040622185116.GA4146@gate.ebshome.net>


On Tue, Jun 22, 2004 at 11:51:16AM -0700, Eugene Surovegin wrote:
> Greg,
>
> IBM PPC 4xx i2c controller doesn't support 0-length transactions (e.g. used by
> SMBUS_QUICK). This patch implements bit-banging emulation for such requests and
> removes temporary kludge added earlier.
>
> Signed-off-by: Eugene Surovegin <ebs@ebshome.net>
>
> Please, apply.

Applied, thanks.

greg k-h

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 18:51 [PATCH] PPC4xx IIC driver: 0-length transactions bit-banging implementation Eugene Surovegin
2005-05-19  6:25 ` [PATCH] PPC4xx IIC driver: 0-length transactions bit-banging Eugene Surovegin
2004-07-08 23:07 ` Greg KH [this message]
2005-05-19  6:25   ` Greg KH

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=20040708230713.GF20431@kroah.com \
    --to=greg@kroah.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sensors@Stimpy.netroedge.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 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.