From: Wolfram Sang <wsa@the-dreams.de>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-i2c@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-pm@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: tvp5150 regression after commit 9f924169c035
Date: Thu, 14 Apr 2016 16:19:45 +0200 [thread overview]
Message-ID: <20160414141945.GA1539@katana> (raw)
In-Reply-To: <570F9DF1.3070700@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
> Yes, I also wonder why I'm the only one facing this issue... maybe no one
> else is using the tvp5150 driver on an OMAP board with mainline?
I wonder why it only affects tvp5150. I don't see the connection yet.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-14 14:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56B204CB.60602@osg.samsung.com>
2016-02-08 10:54 ` tvp5150 regression after commit 9f924169c035 Wolfram Sang
2016-02-12 22:09 ` Javier Martinez Canillas
2016-02-12 22:13 ` Tony Lindgren
2016-02-12 22:28 ` Javier Martinez Canillas
2016-02-12 22:40 ` Tony Lindgren
2016-02-12 23:08 ` Javier Martinez Canillas
2016-02-12 23:46 ` Tony Lindgren
2016-02-13 2:47 ` Javier Martinez Canillas
2016-04-12 22:32 ` Wolfram Sang
2016-04-13 22:39 ` Javier Martinez Canillas
2016-04-14 11:12 ` Wolfram Sang
2016-04-14 13:41 ` Javier Martinez Canillas
2016-04-14 14:19 ` Wolfram Sang [this message]
2016-04-14 14:27 ` Javier Martinez Canillas
2016-04-14 15:12 ` Tony Lindgren
2016-04-14 23:59 ` Javier Martinez Canillas
2016-04-15 14:58 ` Tony Lindgren
2016-04-15 16:48 ` Javier Martinez Canillas
2016-04-15 17:08 ` Tony Lindgren
2016-02-12 22:22 ` Wolfram Sang
2016-02-12 22:26 ` Javier Martinez Canillas
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=20160414141945.GA1539@katana \
--to=wsa@the-dreams.de \
--cc=javier@osg.samsung.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=stern@rowland.harvard.edu \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).