From: "Dan Williams" <dan.j.williams@intel.com>
To: "Voipio Riku" <Riku.Voipio@movial.fi>
Cc: "David Brownell" <david-b@pacbell.net>,
rtc-linux@googlegroups.com,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
"Alessandro Zummo" <alessandro.zummo@towertech.it>,
i2c@lm-sensors.org
Subject: Re: [patch 2.6.19-git] rts-rs5c372 updates: more chips, alarm, 12hr mode, etc
Date: Mon, 11 Dec 2006 16:33:26 -0700 [thread overview]
Message-ID: <e9c3a7c20612111533o75683c2j30dbf440696932a6@mail.gmail.com> (raw)
In-Reply-To: <42003.80.222.56.248.1165875783.squirrel@webmail.movial.fi>
On 12/11/06, Voipio Riku <Riku.Voipio@movial.fi> wrote:
<snip>
> > Have you asked around for anyone who may have insights about i2c-iop3xx
> > driver bugs? Maybe the driver maintainers, or arm-linux folk, or on
> > the i2c list.
>
> I was told to contact Dan Williams, I didn't get any response.
>
Hi Riku, this is the first message I have received.
According to the latest specification update
(http://www.intel.com/design/iio/specupdt/27351910.pdf) there are no
known issues with the i2c. I looked through the thread and did not
see what board you are using, can you send those details?
I have not dealt with the i2c-iop3xx driver in the past. Have you
tried contacting the last person to make functional changes to the
driver?
http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=39288e1ac10b3b9a68a629be67d81a0b53512c4e
Regards,
Dan
next prev parent reply other threads:[~2006-12-11 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 2:59 David Brownell
2006-12-09 9:38 ` [rtc-linux] " Alessandro Zummo
2006-12-11 6:27 ` Voipio Riku
2006-12-11 19:55 ` David Brownell
2006-12-11 22:23 ` Voipio Riku
2006-12-11 23:33 ` Dan Williams [this message]
2006-12-12 8:20 ` David Brownell
2006-12-12 8:39 ` Riku Voipio
2006-12-12 8:30 ` David Brownell
2007-01-03 3:07 ` David Brownell
2007-01-03 22:51 ` Voipio Riku
2007-01-04 4:23 ` David Brownell
2007-01-04 12:05 ` Alessandro Zummo
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=e9c3a7c20612111533o75683c2j30dbf440696932a6@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=Riku.Voipio@movial.fi \
--cc=alessandro.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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
all inboxes | Powered by JetHome®