From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>
Subject: Re: [GIT PULL FOR v5.20] cedrus fix, hantro fixes and destaging
Date: Wed, 27 Jul 2022 20:57:34 +0200 [thread overview]
Message-ID: <20220727205734.77dba501@coco.lan> (raw)
In-Reply-To: <20220727203551.32901319@coco.lan>
Em Wed, 27 Jul 2022 20:35:51 +0200
Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:
> Em Tue, 19 Jul 2022 11:34:55 +0200
> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
>
> > Hi Mauro,
> >
> > This PR has three cedrus/hantro fixes and destages hantro in the final patch.
> > That last patch just moves code into the new directory and has no other changes.
> >
> > Ezequiel, I decided to postpone the v3 of the vb2_find_buffer series to 5.21.
> > It's just an improvement, and the cedrus changes are a bit larger than I'd like
> > so close to the code freeze. I'd like to have those tested first.
>
> It sounds too late to merge it for the upcoming merge window.
>
> So, I applied only patch 1/4:
>
> media: cedrus: hevc: Add check for invalid timestamp
>
> Let's merge the remaining ones after -rc1.
Applied patch 4/4 as well, as this is actually a fix:
hantro: Remove incorrect HEVC SPS validation
Regards,
Mauro
prev parent reply other threads:[~2022-07-27 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 9:34 [GIT PULL FOR v5.20] cedrus fix, hantro fixes and destaging Hans Verkuil
2022-07-19 9:59 ` [GIT PULL FOR v5.20] cedrus fix, hantro fixes and destaging (#84973) Jenkins
2022-07-27 18:35 ` [GIT PULL FOR v5.20] cedrus fix, hantro fixes and destaging Mauro Carvalho Chehab
2022-07-27 18:57 ` 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=20220727205734.77dba501@coco.lan \
--to=mchehab@kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil@xs4all.nl \
--cc=jernej.skrabec@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=paul.kocialkowski@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).