From: Lubomir Rintel <lkundrak@v3.sk>
To: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: A patch slipped through the cracks?
Date: Wed, 20 Sep 2017 19:17:17 +0200 [thread overview]
Message-ID: <1505927837.26708.8.camel@v3.sk> (raw)
Hi,
we're trying to get this reasonably trivial patch [1] applied for more
than a year and four attempts now. (I'm not including it in this
message so that this message won't be ignored for the same reason the
submissions were, whatever they are.)
[1] https://patchwork.linuxtv.org/patch/40862/
I have no idea what went wrong. There was a suspicion (somewhat
confirmed by the initial patch submitter) that spam filtering could
have dropped the first message. Since then the patch did make it to the
list numerous times and was picked up by patchwork.
The patchwork's idea about the patch being "Superseded" is wrong -- I
have no idea why. But someone *please* look into this and apply the
patch.
Thank you
Lubo
next reply other threads:[~2017-09-20 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 17:17 Lubomir Rintel [this message]
2017-09-20 18:06 ` 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=1505927837.26708.8.camel@v3.sk \
--to=lkundrak@v3.sk \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
Powered by JetHome