From: Diederik de Haas <didi.debian@cknow.org>
To: ezequiel@vanguardiasur.com.ar, nicolas.dufresne@collabora.com,
p.zabel@pengutronix.de, mchehab@kernel.org,
m.szyprowski@samsung.com, m.tretter@pengutronix.de,
Benjamin Gaignard <benjamin.gaignard@collabora.com>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
hverkuil-cisco@xs4all.nl, kernel@pengutronix.de,
regressions@lists.linux.dev
Subject: Re: [PATCH] media: verisilicon: Additional fix for the crash when opening the driver
Date: Tue, 23 May 2023 21:58:38 +0200 [thread overview]
Message-ID: <3187393.mvXUDI8C0e@bagend> (raw)
In-Reply-To: <c034db29-b664-793d-35e0-406fdfe2b145@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Tuesday, 23 May 2023 18:36:09 CEST Benjamin Gaignard wrote:
> Diederik, Marek, Michael,
> I have tested this patch on my boards and I see no regressions on
> decoder part and no more crash when probing the encoder.
> Could you test it on your side to confirm it is ok ?
With this patch I'm (also) not seeing the crash
Tested-by: Diederik de Haas <didi.debian@cknow.org>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-23 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230523162528eucas1p297a28b644c81704d7fc9a0810649e3e9@eucas1p2.samsung.com>
2023-05-23 16:25 ` [PATCH] media: verisilicon: Additional fix for the crash when opening the driver Benjamin Gaignard
2023-05-23 16:28 ` Ezequiel Garcia
2023-05-23 16:33 ` Benjamin Gaignard
2023-05-23 16:36 ` Benjamin Gaignard
2023-05-23 17:06 ` Michael Tretter
2023-05-23 17:36 ` Ezequiel Garcia
2023-05-23 23:22 ` Nicolas Dufresne
2023-05-23 19:58 ` Diederik de Haas [this message]
2023-05-24 9:06 ` Thorsten Leemhuis
2023-05-24 9:15 ` Hans Verkuil
2023-05-24 9:22 ` Thorsten Leemhuis
2023-05-24 7:51 ` Marek Szyprowski
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=3187393.mvXUDI8C0e@bagend \
--to=didi.debian@cknow.org \
--cc=benjamin.gaignard@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=m.tretter@pengutronix.de \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=regressions@lists.linux.dev \
/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).