From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-media@vger.kernel.org,
Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: acourbot@chromium.org, tfiga@chromium.org,
hverkuil-cisco@xs4all.nl,
Sebastian Fricke <sebastian.fricke@collabora.com>,
Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chen-Yu Tsai <wens@csie.org>,
"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
"moderated list:ARM/Allwinner sunXi SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Allwinner sunXi SoC support"
<linux-sunxi@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3 2/2] staging: media: cedrus: Rename H265 to HEVC
Date: Mon, 28 Mar 2022 19:09:11 +0200 [thread overview]
Message-ID: <4697363.GXAFRqVoOG@jernej-laptop> (raw)
In-Reply-To: <20220327084308.9053-3-sebastian.fricke@collabora.com>
Hi Sebastian!
Dne nedelja, 27. marec 2022 ob 10:43:10 CEST je Sebastian Fricke napisal(a):
> Rename all instances where the identifier H265 is used with HEVC.
> The codec has multiple identifiers H.265 (ITU-T), MPEG-H Part 2 (ISO),
> but the actual name of the codec is HEVC (High Efficiency Video Coding).
> Also nearly all other related drivers use the term HEVC instead of H265.
>
> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com>
This patch is not constructive. I admit, it's unfortunate it's not using same
name as other drivers, but anyone dealing with HEVC will know H265 is synonym
for it. This patch doesn't improve anything and actually makes any fix harder
to backport, if something cames up. According to diffstat, this rewrites more
than 50% of cedrus_h265.c, including renaming the file. Additionally, it's easy
to miss something to rename and we could play this game in the future too, for
no real benefit.
So NAK.
Best regard,
Jernej
P.S. Please wait at least few days before resending patches, even if you find
something. After all, RFC patches are meant to get some response, it's not
expected they will be perfect.
> ---
> drivers/staging/media/sunxi/cedrus/Makefile | 2 +-
> drivers/staging/media/sunxi/cedrus/cedrus.c | 30 +-
> drivers/staging/media/sunxi/cedrus/cedrus.h | 14 +-
> .../staging/media/sunxi/cedrus/cedrus_dec.c | 10 +-
> .../cedrus/{cedrus_h265.c => cedrus_hevc.c} | 438 +++++++++---------
> .../staging/media/sunxi/cedrus/cedrus_hw.c | 4 +-
> .../staging/media/sunxi/cedrus/cedrus_regs.h | 394 ++++++++--------
> .../staging/media/sunxi/cedrus/cedrus_video.c | 4 +-
> 8 files changed, 448 insertions(+), 448 deletions(-)
> rename drivers/staging/media/sunxi/cedrus/{cedrus_h265.c => cedrus_hevc.c}
> (53%)
next prev parent reply other threads:[~2022-03-28 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 8:43 [RFC PATCH v3 0/2] HEVC enhancements Sebastian Fricke
2022-03-27 8:43 ` [RFC PATCH v3 1/2] media: docs-rst: Append HEVC specific term Sebastian Fricke
2022-03-28 17:10 ` Jernej Škrabec
2022-03-27 8:43 ` [RFC PATCH v3 2/2] staging: media: cedrus: Rename H265 to HEVC Sebastian Fricke
2022-03-28 17:09 ` Jernej Škrabec [this message]
2022-03-29 6:53 ` Sebastian Fricke
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=4697363.GXAFRqVoOG@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=acourbot@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--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=paul.kocialkowski@bootlin.com \
--cc=sebastian.fricke@collabora.com \
--cc=tfiga@chromium.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