From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"Samuel Holland" <samuel@sholland.org>,
"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
"Hans Verkuil" <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v1] media: cedrus: Propagate error code from cedrus_h265_skip_bits()
Date: Tue, 25 Oct 2022 12:34:56 +0300 [thread overview]
Message-ID: <3a26e105-9c50-8cdd-b4be-ba97b3306261@collabora.com> (raw)
In-Reply-To: <12078224.O9o76ZdvQC@jernej-laptop>
On 10/25/22 07:59, Jernej Škrabec wrote:
> Dne ponedeljek, 24. oktober 2022 ob 13:38:36 CEST je Hans Verkuil napisal(a):
>> Hi Dmitry,
>>
>> This patch has a conflict with this patch from Jernej:
>>
>> https://patchwork.linuxtv.org/project/linux-media/patch/20221017194413.11983
>> 01-1-jernej.skrabec@gmail.com/
>>
>> I decided to take Jernej's patch first. Can you make a v2 that sits on top
>> of that patch?
> I believe you already merged first version of the patch for 6.1. No need for
> this version though, first version already solves main issue.
That was a followup to the first version.
--
Best regards,
Dmitry
next prev parent reply other threads:[~2022-10-25 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 15:01 [PATCH v1] media: cedrus: Propagate error code from cedrus_h265_skip_bits() Dmitry Osipenko
2022-10-24 11:38 ` Hans Verkuil
2022-10-25 4:59 ` Jernej Škrabec
2022-10-25 9:34 ` Dmitry Osipenko [this message]
2022-10-25 10:23 ` Hans Verkuil
2022-10-25 10:36 ` Dmitry Osipenko
2022-10-25 10:41 ` Hans Verkuil
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=3a26e105-9c50-8cdd-b4be-ba97b3306261@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jernej.skrabec@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=samuel@sholland.org \
--cc=wens@csie.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