From: Matthias Schwarzott <zzam@gentoo.org>
To: crope@iki.fi, linux-media@vger.kernel.org
Subject: Re: [PATCH] cx23885: Split Hauppauge WinTV Starburst from HVR4400 card entry
Date: Sun, 21 Dec 2014 21:07:02 +0100 [thread overview]
Message-ID: <54972866.3030101@gentoo.org> (raw)
In-Reply-To: <1419191964-29833-1-git-send-email-zzam@gentoo.org>
Hi!
Should the commit message directly point to the breaking commit
36efec48e2e6016e05364906720a0ec350a5d768?
This commit hopefully reverts the problematic attach for the Starburst
card. I kept the GPIO-part in common, but I can split this also if
necessary.
Regards
Matthias
next prev parent reply other threads:[~2014-12-21 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 19:59 [PATCH] cx23885: Split Hauppauge WinTV Starburst from HVR4400 card entry Matthias Schwarzott
2014-12-21 20:07 ` Matthias Schwarzott [this message]
2014-12-22 13:25 ` Mauro Carvalho Chehab
2014-12-22 13:36 ` Matthias Schwarzott
2014-12-22 14:01 ` Antti Palosaari
2014-12-22 14:12 ` Steven Toth
2014-12-21 20:27 ` Antti Palosaari
2014-12-22 12:59 ` Steven Toth
2014-12-22 13:06 ` Matthias Schwarzott
2014-12-22 13:12 ` Steven Toth
-- strict thread matches above, loose matches on Subject: below --
2014-12-22 22:51 Matthias Schwarzott
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=54972866.3030101@gentoo.org \
--to=zzam@gentoo.org \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.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).