From: Greg KH <greg@kroah.com>
To: Kumar Gala <galak@somerset.sps.mot.com>
Cc: linuxppc-embedded@ozlabs.org, sensors@Stimpy.netroedge.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] I2C-MPC: use wait_event_interruptible_timeout between transactions
Date: Fri, 14 Jan 2005 10:41:46 -0800 [thread overview]
Message-ID: <20050114184146.GA30093@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501131816260.27470@blarg.somerset.sps.mot.com>
On Thu, Jan 13, 2005 at 06:21:54PM -0600, Kumar Gala wrote:
> Use wait_event_interruptible_timeout so we dont waste time waiting between
> transactions like we use to. Also, we use the adapters timeout so the
> ioctl cmd I2C_TIMEOUT will now work.
Applied, thanks.
greg k-h
next prev parent reply other threads:[~2005-01-14 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 0:21 [PATCH] I2C-MPC: use wait_event_interruptible_timeout between transactions Kumar Gala
2005-01-14 18:41 ` Greg KH [this message]
2005-01-17 21:46 [PATCH] I2C: Improve it87 super-i/o detection Greg KH
2005-01-17 21:46 ` [PATCH] I2C-MPC: use wait_event_interruptible_timeout between transactions 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=20050114184146.GA30093@kroah.com \
--to=greg@kroah.com \
--cc=galak@somerset.sps.mot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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 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).