From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
tiffany.lin@mediatek.com, andrew-ct.chen@mediatek.com,
mchehab@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.co.uk
Cc: linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH] media: platform: mtk-vcodec: Do not force /dev/videoX node number
Date: Wed, 19 Jan 2022 10:10:42 +0100 [thread overview]
Message-ID: <72ac959b-ad5f-8f4e-38d1-3da9d9866290@collabora.com> (raw)
In-Reply-To: <20220118150717.706074-1-benjamin.gaignard@collabora.com>
Il 18/01/22 16:07, Benjamin Gaignard ha scritto:
> Let's v4l2 framework use a free /dev/videoX node for decode and encoder.
> For the decoder call video_register_device() before register the media
> controller device so the mapping between ins correctly done.
> Since the registering sequence has changed rework exiting errors case too.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Hello Benjamin,
please add the following Fixes tags to this commit:
Fixes: 590577a4e525 ("[media] vcodec: mediatek: Add Mediatek V4L2 Video Decoder
Driver")
Fixes: 4e855a6efa54 ("[media] vcodec: mediatek: Add Mediatek V4L2 Video Encoder
Driver")
After that..
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
prev parent reply other threads:[~2022-01-19 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 15:07 Benjamin Gaignard
2022-01-19 9:10 ` AngeloGioacchino Del Regno [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=72ac959b-ad5f-8f4e-38d1-3da9d9866290@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.co.uk \
--cc=benjamin.gaignard@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=tiffany.lin@mediatek.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
all inboxes | Powered by JetHome®