linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Gusev <ronne-cmBhpYW9OiY@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Benjamin Herrenschmidt
	<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Subject: Re: Error ' I2C transfer at 0x48 failed' on 2.6.33
Date: Sun, 28 Feb 2010 16:00:02 +0300	[thread overview]
Message-ID: <20100228160002.14783f4a@power-debian> (raw)
In-Reply-To: <20100227100420.1016e0c1-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

В Sat, 27 Feb 2010 10:04:20 +0100
Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> пишет:

> Hi Andrey,
> 
> On Sat, 27 Feb 2010 00:49:53 +0300, Andrey Gusev wrote:
> > Hello all!
> > 
> > Thera are errors in dmeg on 2.6.33:
> > 
> ....
> ....
> I have good news for you: the error messages are harmless and can be
> safely ignored. I presume you did not notice any functional problem. I
> made the i2c-powermac driver more verbose for debugging purposes and
> it appears I've made it a little too verbose in the non-debugging
> case. Sorry about that.
> 
> The patch below should fix it, if you have the chance to give it a
> try:
> 

Hi!

I didn't noted ant functional problem, but this looked like regression
and I decided to report about it. I'll try patch.

Thanks,
Andrey

  parent reply	other threads:[~2010-02-28 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 21:49 Error ' I2C transfer at 0x48 failed' on 2.6.33 Andrey Gusev
2010-02-27  9:04 ` Jean Delvare
     [not found]   ` <20100227100420.1016e0c1-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-02-28 13:00     ` Andrey Gusev [this message]
2010-03-01 10:50       ` 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=20100228160002.14783f4a@power-debian \
    --to=ronne-cmbhpyw9oiy@public.gmane.org \
    --cc=benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).