From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: hverkuil-cisco@xs4all.nl, mchehab+huawei@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] media: cec: CEC 2.0-only bcast messages were ignored" failed to apply to 5.5-stable tree
Date: Sun, 9 Feb 2020 13:13:50 -0500 [thread overview]
Message-ID: <20200209181350.GL3584@sasha-vm> (raw)
In-Reply-To: <1581248809208186@kroah.com>
On Sun, Feb 09, 2020 at 12:46:49PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.5-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 01d4fb115470e9f88a58975fe157a9e8b214dfe5 Mon Sep 17 00:00:00 2001
>From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>Date: Wed, 4 Dec 2019 08:52:08 +0100
>Subject: [PATCH] media: cec: CEC 2.0-only bcast messages were ignored
>
>Some messages are allowed to be a broadcast message in CEC 2.0
>only, and should be ignored by CEC 1.4 devices.
>
>Unfortunately, the check was wrong, causing such messages to be
>marked as invalid under CEC 2.0.
>
>Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>Cc: <stable@vger.kernel.org> # for v4.10 and up
>Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Looks like we somehow ended up with duplicate commits upstream:
cec935ce69fc ("media: cec: CEC 2.0-only bcast messages were ignored")
01d4fb115470 ("media: cec: CEC 2.0-only bcast messages were ignored")
cec935ce69fc is already queued for all relevant trees, so nothing to do
here.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-09 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 11:46 FAILED: patch "[PATCH] media: cec: CEC 2.0-only bcast messages were ignored" failed to apply to 5.5-stable tree gregkh
2020-02-09 18:13 ` Sasha Levin [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=20200209181350.GL3584@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=mchehab+huawei@kernel.org \
--cc=stable@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.