From: Florent AUDEBERT <florent.audebert@anevia.com>
To: linux-media@vger.kernel.org
Cc: abraham.manu@gmail.com, Florent Audebert <faudebert@anevia.com>
Subject: Re: [PATCH] stb0899: Removed an extra byte sent at init on DiSEqC bus
Date: Tue, 19 Oct 2010 14:55:31 +0200 [thread overview]
Message-ID: <4CBD9543.2050107@anevia.com> (raw)
In-Reply-To: <4C125DD5.6060604@anevia.com>
On 06/11/2010 06:01 PM, Florent AUDEBERT wrote:
> I noticed a stray 0x00 at init on DiSEqC bus (KNC1 DVB-S2) with a DiSEqC
> tool analyzer.
>
> I removed the register from initialization table and all seem to go well
> (at least for my KNC board).
Hi,
This old small patch had been marked superseded on patchwork[1].
Is there an non-obvious case when patches go superseded ? Perhaps I missed
something but it seems to me no other patch replaced it.
Regards,
[1] https://patchwork.kernel.org/patch/105621/
--
Florent AUDEBERT
next prev parent reply other threads:[~2010-10-19 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 16:01 [PATCH] stb0899: Removed an extra byte sent at init on DiSEqC bus Florent AUDEBERT
2010-10-19 12:55 ` Florent AUDEBERT [this message]
2010-10-19 16:05 ` Mauro Carvalho Chehab
2011-06-01 13:57 ` Mauro Carvalho Chehab
2011-06-01 16:24 ` Manu Abraham
2011-06-01 18:56 ` Mauro Carvalho Chehab
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=4CBD9543.2050107@anevia.com \
--to=florent.audebert@anevia.com \
--cc=abraham.manu@gmail.com \
--cc=faudebert@anevia.com \
--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