From: Troy Kisky <troy.kisky-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 3/3] I2C: DaVinci: fix signal handling bug
Date: Fri, 02 May 2008 13:41:43 -0700 [thread overview]
Message-ID: <481B7C87.5020405@boundarydevices.com> (raw)
In-Reply-To: <20080502160540.2367669e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
Jean Delvare wrote:
>
> Looks much better than your first attempt. I'm taking this in my i2c
> tree, thanks.
>
Thanks for all your efforts in improving this driver.
Troy
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-05-02 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 23:53 [PATCH 1/3] I2C: DaVinci: move dev_debug line for more output Troy Kisky
[not found] ` <1209599638-17057-1-git-send-email-troy.kisky-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2008-04-30 23:53 ` [PATCH 2/3] I2C: DaVinci: initialize cmd_complete sooner Troy Kisky
[not found] ` <1209599638-17057-2-git-send-email-troy.kisky-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2008-04-30 23:53 ` [PATCH 3/3] I2C: DaVinci: fix signal handling bug Troy Kisky
[not found] ` <1209599638-17057-3-git-send-email-troy.kisky-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2008-05-02 14:05 ` Jean Delvare
[not found] ` <20080502160540.2367669e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-05-02 20:41 ` Troy Kisky [this message]
[not found] ` <481B7C87.5020405-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2008-05-02 20:47 ` Jean Delvare
2008-05-02 13:46 ` [PATCH 1/3] I2C: DaVinci: move dev_debug line for more output Jean Delvare
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=481B7C87.5020405@boundarydevices.com \
--to=troy.kisky-q5rjgjkts06cy9shamctrueocmrvltnr@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.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