From: "shekhar, chandra" <x0044955@ti.com>
To: Jason Marini <jason.marini@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1] Patch for I2C transmit overflow error
Date: Fri, 9 Jan 2009 08:41:47 +0530 [thread overview]
Message-ID: <102501c97208$02bd8750$LocalHost@wipultra806> (raw)
In-Reply-To: 423644ca0901061212i280eff36o61def6fb812b6bd7@mail.gmail.com
----- Original Message -----
From: "Jason Marini" <jason.marini@gmail.com>
To: <linux-omap@vger.kernel.org>
Sent: Wednesday, January 07, 2009 1:42 AM
Subject: Re: [PATCH 1/1] Patch for I2C transmit overflow error
>>>This patch is to fix I2C transmit overflow error.
>>>I guess it should fix the OSK5912 error. I dont have the board to test it.
>>
>>Yes, it makes those error reports go away. I'd say to merge this patch.
>
> Chandra, why would the transmit underflow (XDR) status sometimes be
> set at the same time as the XRDY status?
I dint say XDR and XRDY.
Its XDR and XUDF being set simultaneously.
Why would you want to ignore
> XDR (using 'continue') if XRDY is set?
>
So i am not ignoring any XDR. :)
> Thank you in advance for clearing this up for me.
>
> -Jason Marini
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-01-09 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 20:12 [PATCH 1/1] Patch for I2C transmit overflow error Jason Marini
2009-01-09 3:11 ` shekhar, chandra [this message]
2009-01-09 13:19 ` Jason Marini
2009-01-09 15:07 ` shekhar, chandra
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 14:10 chandra shekhar
2008-08-07 23:38 ` David Brownell
2008-08-08 6:19 ` Tony Lindgren
2008-08-08 8:01 ` David Brownell
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='102501c97208$02bd8750$LocalHost@wipultra806' \
--to=x0044955@ti.com \
--cc=jason.marini@gmail.com \
--cc=linux-omap@vger.kernel.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