From: Knut Petersen <Knut_Petersen@t-online.de>
To: Hans Verkuil <hansverk@cisco.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [REGRESSION 3.11-rc] wm8775 9-001b: I2C: cannot write ??? to register R??
Date: Wed, 28 Aug 2013 07:34:49 +0200 [thread overview]
Message-ID: <521D8BF9.7070704@t-online.de> (raw)
In-Reply-To: <521C7697.6070809@cisco.com>
On 27.08.2013 11:51, Hans Verkuil wrote:
> On 08/27/2013 11:35 AM, Knut Petersen wrote:
>> On 27.08.2013 09:26, Hans Verkuil wrote:
>>> On 08/25/2013 05:45 PM, Knut Petersen wrote:
>>>> Booting current git kernel dmesg shows a set of new warnings:
>>>>
>>>> "wm8775 9-001b: I2C: cannot write ??? to register R??"
>>>>
>>>> Nevertheless, the hardware seems to work fine.
>>>>
>>>> This is a new problem, introduced after kernel 3.10.
>>>> If necessary I can bisect.
>>> Can you try this patch? I'm pretty sure this will fix it.
>> Indeed, it does cure the problem. Thanks.
>>
>> Tested-by: Knut Petersen <Knut_Petersen@t-online.de>
> Thanks for testing this! I've posted the pull request for this.
> Hopefully it will make 3.11 before it is released.
As I wrote in the initial bug report, the problem has been introduced _after_ kernel 3.10,
facd23664f1d63c33fbc6da52261c8548ed3fbd4 is _not_ part of kernel 3.10.x
Therefore the CC to stable@vger.kernel.org for v3.10 in
b9a1dfd3ba3ae00b0c1d1a396ed43fac85a32990 is wrong.
cu,
Knut
> Regards,
>
> Hans
>
>
next prev parent reply other threads:[~2013-08-28 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 15:45 [REGRESSION 3.11-rc] wm8775 9-001b: I2C: cannot write ??? to register R?? Knut Petersen
2013-08-27 7:26 ` Hans Verkuil
2013-08-27 9:35 ` Knut Petersen
2013-08-27 9:51 ` Hans Verkuil
2013-08-28 5:34 ` Knut Petersen [this message]
2013-08-31 8:00 ` [REGRESSION 3.11-rc1+] " Knut Petersen
2013-08-31 16:51 ` Linus Torvalds
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=521D8BF9.7070704@t-online.de \
--to=knut_petersen@t-online.de \
--cc=hansverk@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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