From: Antti Palosaari <crope@iki.fi>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-media@vger.kernel.org, Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH] rtl2830: add parent for I2C adapter
Date: Wed, 30 Oct 2013 18:29:47 +0200 [thread overview]
Message-ID: <527133FB.2030404@iki.fi> (raw)
In-Reply-To: <20131030160234.GE3663@katana>
On 30.10.2013 18:02, Wolfram Sang wrote:
>
>>> Well, I intentionally asked for revert not bisect. Removing the #ifdef
>>> can easily be done by hand if needed and will just need one recompile to
>>> make sure.
>>
>> Yes, but compiling whole Kernel is always pain. I dont certainly
>> want to do that just for testing some patches.
>
> Well, if you ask for support for debugging, you should be prepared to do
> exactly that.
>
>> Jean jsut pointed out on IRC that this patch likely fixes the issue:
>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=47b6e477ed4ecacddd1f82d04d686026e08dc3db
>
> Yup, he is right. You have ACPI enabled.
>
>> As that patch is already applied to 3.12 it should be fine. I was
>> running media master which is based 3.12-rc2.
>
> Asking you to build the latest kernel might have been another thing I'd
> ask you to do.
I installed that single patch top of media master tree and it fixes the
problem. Maybe this is enough If there is still good reason to latest
Linus tree I can do that too.
RTL2830 adapter parent patch will go to the 3.13.
Thanks Jean and Wolfram
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2013-10-30 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 20:12 [PATCH] rtl2830: add parent for I2C adapter Antti Palosaari
2013-10-21 20:20 ` Antti Palosaari
2013-10-29 21:17 ` Antti Palosaari
2013-10-30 15:16 ` Wolfram Sang
2013-10-30 15:35 ` Antti Palosaari
2013-10-30 15:36 ` Antti Palosaari
2013-10-30 15:45 ` Wolfram Sang
2013-10-30 15:51 ` Antti Palosaari
2013-10-30 16:02 ` Wolfram Sang
2013-10-30 16:29 ` Antti Palosaari [this message]
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=527133FB.2030404@iki.fi \
--to=crope@iki.fi \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).