From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "nibble.max" <nibble.max@gmail.com>
Cc: Antti Palosaari <crope@iki.fi>,
"Igor M. Liplianin" <liplianin@me.by>,
Konstantin Dimitrov <kosio.dimitrov@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: How to add patch for M88TS2022 tuner and M88DS3103 DVB-S2 demodulator code?
Date: Mon, 06 Aug 2012 14:27:01 -0300 [thread overview]
Message-ID: <501FFE65.6020602@redhat.com> (raw)
In-Reply-To: <201207091714268753186@gmail.com>
Em 09-07-2012 06:14, nibble.max escreveu:
> Hello Mauro,
> I try to add the patch for new M88TS2022 tuner and M88DS3103 demodulator again.
> As I remember that Konstantin submitted the patch for spliting ds3000 code into the tuner and demodulator files.
> I can find it in the linux-media mail list.
The patches didn't reach patchwork, as they were line-wrapped.
I reviewed the patches today.
> But it is failure to find it in the latest code from LinuxTV.org and kernel org, and even in Patchwork of LINUXTV.
> As the previous discussion that some of my patch should base on Konstantin's patch.
> What is the status of Konstantin's patch?
> And what is the start point for me to add patch for M88TS2022 and M88DS3103 code?
Let's wait for Konstantin's new patches.
>
> BR,
> --------------
> nibble.max
> 2012-07-09
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-08-06 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 9:14 How to add patch for M88TS2022 tuner and M88DS3103 DVB-S2 demodulator code? nibble.max
2012-08-06 17:27 ` Mauro Carvalho Chehab [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=501FFE65.6020602@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=kosio.dimitrov@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
--cc=nibble.max@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.