linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@collabora.com>
To: linux-media@vger.kernel.org
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
	kernel@collabora.com, Ezequiel Garcia <ezequiel@collabora.com>
Subject: [PATCH 00/10] Correct return type for mem2mem buffer helpers
Date: Fri,  8 Feb 2019 13:17:38 -0300	[thread overview]
Message-ID: <20190208161748.5862-1-ezequiel@collabora.com> (raw)

As the subject says, we want to fix the return type
of these mem2mem buffer helpers. They are currently returning
a void pointer, which prevents type checking.

The patchset turned out to be much bigger than I was expecting,
so it's splitted in per-driver patches.

It'd be awesome if driver maintainers can take review
the changes.

Thanks!

Ezequiel Garcia (10):
  mtk-jpeg: Correct return type for mem2mem buffer helpers
  mtk-mdp: Correct return type for mem2mem buffer helpers
  mtk-vcodec: Correct return type for mem2mem buffer helpers
  mx2_emmaprp: Correct return type for mem2mem buffer helpers
  rockchip/rga: Correct return type for mem2mem buffer helpers
  s5p-g2d: Correct return type for mem2mem buffer helpers
  s5p-jpeg: Correct return type for mem2mem buffer helpers
  sh_veu: Correct return type for mem2mem buffer helpers
  rockchip/vpu: Correct return type for mem2mem buffer helpers
  media: v4l2-mem2mem: Correct return type for mem2mem buffer helpers

 .../media/platform/mtk-jpeg/mtk_jpeg_core.c   | 40 +++++------
 drivers/media/platform/mtk-mdp/mtk_mdp_m2m.c  | 20 ++----
 .../platform/mtk-vcodec/mtk_vcodec_dec.c      | 62 +++++++---------
 .../platform/mtk-vcodec/mtk_vcodec_enc.c      | 72 ++++++++-----------
 drivers/media/platform/mx2_emmaprp.c          |  6 +-
 drivers/media/platform/rockchip/rga/rga.c     |  6 +-
 drivers/media/platform/s5p-g2d/g2d.c          |  6 +-
 drivers/media/platform/s5p-jpeg/jpeg-core.c   | 38 +++++-----
 drivers/media/platform/sh_veu.c               |  4 +-
 drivers/media/v4l2-core/v4l2-mem2mem.c        |  6 +-
 .../rockchip/vpu/rk3288_vpu_hw_jpeg_enc.c     |  6 +-
 .../rockchip/vpu/rk3399_vpu_hw_jpeg_enc.c     |  6 +-
 include/media/v4l2-mem2mem.h                  | 18 ++---
 13 files changed, 129 insertions(+), 161 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-02-08 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 16:17 Ezequiel Garcia [this message]
2019-02-08 16:17 ` [PATCH 01/10] mtk-jpeg: Correct return type for mem2mem buffer helpers Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 02/10] mtk-mdp: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 03/10] mtk-vcodec: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 04/10] mx2_emmaprp: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 05/10] rockchip/rga: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 06/10] s5p-g2d: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 07/10] s5p-jpeg: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 08/10] sh_veu: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 09/10] rockchip/vpu: " Ezequiel Garcia
2019-02-08 16:17 ` [PATCH 10/10] media: v4l2-mem2mem: " Ezequiel Garcia

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=20190208161748.5862-1-ezequiel@collabora.com \
    --to=ezequiel@collabora.com \
    --cc=hans.verkuil@cisco.com \
    --cc=kernel@collabora.com \
    --cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).