public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, r-woodruff2@ti.com
Subject: Re: [PATCH] i2c-omap: fix I2C timeouts due to recursive omap_i2c_{un,}idle()
Date: Fri, 10 Oct 2008 14:29:45 -0700	[thread overview]
Message-ID: <200810101429.45548.david-b@pacbell.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0810101056020.13922@utopia.booyaka.com>

On Friday 10 October 2008, Paul Walmsley wrote:
> Problem reported by David Brownell <david-b@pacbell.net>.

Hmm, seems to solve the problem for me too... though for
the life of me I can't quite see how that explains all
the symptoms I've observed.  I'll keep an eye out to see
what comes up over time; I could believe this is only one
of the problems lurking here.

- Dave




  parent reply	other threads:[~2008-10-10 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 16:58 [PATCH] i2c-omap: fix I2C timeouts due to recursive omap_i2c_{un,}idle() Paul Walmsley
2008-10-10 17:48 ` Steve Sakoman
2008-10-10 21:29 ` David Brownell [this message]
2008-10-11 14:58   ` Tony Lindgren

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=200810101429.45548.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@ti.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