After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773497 - vaapi: miscellaneous code style fixes
vaapi: miscellaneous code style fixes
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
unspecified
Other All
: Normal enhancement
: 1.10.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-10-25 17:04 UTC by Víctor Manuel Jáquez Leal
Modified: 2016-10-31 14:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
plugins: simplify code (941 bytes, patch)
2016-10-25 17:04 UTC, Víctor Manuel Jáquez Leal
none Details | Review
encode: h264, h265: rename long name (2.24 KB, patch)
2016-10-25 17:04 UTC, Víctor Manuel Jáquez Leal
none Details | Review
vaapivideomemory: rename input parameter (2.00 KB, patch)
2016-10-25 17:04 UTC, Víctor Manuel Jáquez Leal
none Details | Review
vaapivideomemory: comment style (961 bytes, patch)
2016-10-25 17:05 UTC, Víctor Manuel Jáquez Leal
none Details | Review
plugins: fix code style for errors (6.34 KB, patch)
2016-10-25 17:05 UTC, Víctor Manuel Jáquez Leal
none Details | Review
vaapidecode: rename member to allowed_sinkpad_caps (3.77 KB, patch)
2016-10-25 17:05 UTC, Víctor Manuel Jáquez Leal
none Details | Review
vaapipostproc: use GST_*_OBJECT when possible (5.51 KB, patch)
2016-10-25 17:05 UTC, Víctor Manuel Jáquez Leal
none Details | Review
plugins: simplify code (941 bytes, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
committed Details | Review
vaapiencode: h264, h265: rename codec name (2.24 KB, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
committed Details | Review
vaapidecode: rename long name (1.07 KB, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
none Details | Review
vaapivideomemory: rename input parameter (2.00 KB, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
committed Details | Review
vaapivideomemory: comment style (961 bytes, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
committed Details | Review
plugins: fix code style for errors (6.34 KB, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
committed Details | Review
vaapidecode: rename member to allowed_sinkpad_caps (3.72 KB, patch)
2016-10-25 17:27 UTC, Víctor Manuel Jáquez Leal
committed Details | Review
vaapipostproc: use GST_*_OBJECT when possible (5.51 KB, patch)
2016-10-25 17:28 UTC, Víctor Manuel Jáquez Leal
committed Details | Review

Description Víctor Manuel Jáquez Leal 2016-10-25 17:04:29 UTC
These patches are not related directly to a specific bug, but rather
they are cleanups to the code, somewhat required for further developments.
Comment 1 Víctor Manuel Jáquez Leal 2016-10-25 17:04:33 UTC
Created attachment 338434 [details] [review]
plugins: simplify code

Merge two lines of variable declarations.
Comment 2 Víctor Manuel Jáquez Leal 2016-10-25 17:04:50 UTC
Created attachment 338435 [details] [review]
encode: h264, h265: rename long name

So encoder and decoders have the same codec name.
Comment 3 Víctor Manuel Jáquez Leal 2016-10-25 17:04:56 UTC
Created attachment 338436 [details] [review]
vaapivideomemory: rename input parameter

In order to clarify the use of flag as input parameter, it is renamed to
surface_alloc_flag, since it is used when creating a VA surface with certain
properties.
Comment 4 Víctor Manuel Jáquez Leal 2016-10-25 17:05:03 UTC
Created attachment 338437 [details] [review]
vaapivideomemory: comment style
Comment 5 Víctor Manuel Jáquez Leal 2016-10-25 17:05:08 UTC
Created attachment 338438 [details] [review]
plugins: fix code style for errors
Comment 6 Víctor Manuel Jáquez Leal 2016-10-25 17:05:14 UTC
Created attachment 338439 [details] [review]
vaapidecode: rename member to allowed_sinkpad_caps

vaapidecode has a member named allowed_caps, but this name is not enough
explicit. This patch renames allowed_caps to allowed_sinkpad_caps.

No functional changes were included.

https://bugzilla.gnome.org/show_bug.cgi?id=772838
Comment 7 Víctor Manuel Jáquez Leal 2016-10-25 17:05:21 UTC
Created attachment 338440 [details] [review]
vaapipostproc: use GST_*_OBJECT when possible

Since we can have several vaapipostproc operating in a pipeline, it is useful
to know which one is generating the logging message.
Comment 8 Víctor Manuel Jáquez Leal 2016-10-25 17:27:07 UTC
Created attachment 338445 [details] [review]
plugins: simplify code

Merge two lines of variable declarations.
Comment 9 Víctor Manuel Jáquez Leal 2016-10-25 17:27:14 UTC
Created attachment 338446 [details] [review]
vaapiencode: h264, h265: rename codec name

So encoder and decoders have the same codec name.
Comment 10 Víctor Manuel Jáquez Leal 2016-10-25 17:27:25 UTC
Created attachment 338447 [details] [review]
vaapidecode: rename long name

So encoders and decoders have similar long names.
Comment 11 Víctor Manuel Jáquez Leal 2016-10-25 17:27:32 UTC
Created attachment 338448 [details] [review]
vaapivideomemory: rename input parameter

In order to clarify the use of flag as input parameter, it is renamed to
surface_alloc_flag, since it is used when creating a VA surface with certain
properties.
Comment 12 Víctor Manuel Jáquez Leal 2016-10-25 17:27:39 UTC
Created attachment 338449 [details] [review]
vaapivideomemory: comment style
Comment 13 Víctor Manuel Jáquez Leal 2016-10-25 17:27:46 UTC
Created attachment 338450 [details] [review]
plugins: fix code style for errors
Comment 14 Víctor Manuel Jáquez Leal 2016-10-25 17:27:54 UTC
Created attachment 338451 [details] [review]
vaapidecode: rename member to allowed_sinkpad_caps

vaapidecode has a member named allowed_caps, but this name is not enough
explicit. This patch renames allowed_caps to allowed_sinkpad_caps.

No functional changes were included.
Comment 15 Víctor Manuel Jáquez Leal 2016-10-25 17:28:01 UTC
Created attachment 338452 [details] [review]
vaapipostproc: use GST_*_OBJECT when possible

Since we can have several vaapipostproc operating in a pipeline, it is useful
to know which one is generating the logging message.
Comment 16 Víctor Manuel Jáquez Leal 2016-10-25 17:40:29 UTC
Attachment 338445 [details] pushed as 4f4e0a8 - plugins: simplify code
Attachment 338446 [details] pushed as 43dd4b7 - vaapiencode: h264, h265: rename codec name
Attachment 338448 [details] pushed as 289a8e5 - vaapivideomemory: rename input parameter
Attachment 338449 [details] pushed as 34e8579 - vaapivideomemory: comment style
Attachment 338450 [details] pushed as 0f938be - plugins: fix code style for errors
Attachment 338451 [details] pushed as c258343 - vaapidecode: rename member to allowed_sinkpad_caps
Attachment 338452 [details] pushed as bb0abb1 - vaapipostproc: use GST_*_OBJECT when possible