From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: Florent AUDEBERT <florent.audebert@anevia.com>, abraham.manu@gmail.com
Cc: linux-media@vger.kernel.org, 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:05:32 -0200 [thread overview]
Message-ID: <4CBDC1CC.6030704@gmail.com> (raw)
In-Reply-To: <4CBD9543.2050107@anevia.com>
Em 19-10-2010 10:55, Florent AUDEBERT escreveu:
> 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.
This is one of the bad things with patchwork: there's no "reason" field associated
to a status change, nor it marks when the status were changed.
A search on my linux-media box, showed that this patch were there, waiting for
Manu review, at the email I sent on Jul, 6 2010. The patch still applies, and
I didn't find any reply from Manu giving any feedback about it.
So, I'm re-tagging it as under review.
Manu, any comments about this patch (and the other remaining patches that we're
waiting fro your review) ?
>
>
> Regards,
>
>
> [1] https://patchwork.kernel.org/patch/105621/
>
Cheers,
Mauro
next prev parent reply other threads:[~2010-10-19 16:05 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
2010-10-19 16:05 ` Mauro Carvalho Chehab [this message]
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=4CBDC1CC.6030704@gmail.com \
--to=maurochehab@gmail.com \
--cc=abraham.manu@gmail.com \
--cc=faudebert@anevia.com \
--cc=florent.audebert@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 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.