From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org,
Mike Ditto <mditto@consentry.com>
Subject: Re: Calling wait_event_interruptible_timeout() in I2C wait functions
Date: Thu, 5 Feb 2009 09:18:04 -0600 [thread overview]
Message-ID: <ed82fe3e0902050718w1c7bfff3r883eea185b66299@mail.gmail.com> (raw)
In-Reply-To: <20090205115100.GD422@sirena.org.uk>
On Thu, Feb 5, 2009 at 5:51 AM, Mark Brown <broonie@sirena.org.uk> wrote:
> This is exactly the problem for users that caused Timur to run into this
> - further up the stack we're trying to do cleanup that involves writing
> via I2C but the I2C writes error out due to the signal.
Well, there's not much discussion on this issue, so I'm going to make
the change to an uninterruptible wait and see if it fixes my problem.
If so, I'll post a patch for i2c-mpc.c and see how far I get.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2009-02-05 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 19:37 Calling wait_event_interruptible_timeout() in I2C wait functions Timur Tabi
2009-02-04 20:00 ` Mike Ditto
2009-02-05 11:51 ` Mark Brown
2009-02-05 15:18 ` Timur Tabi [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=ed82fe3e0902050718w1c7bfff3r883eea185b66299@mail.gmail.com \
--to=timur@freescale.com \
--cc=broonie@sirena.org.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mditto@consentry.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).