All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: linux-media@vger.kernel.org
Subject: [PATCH 0/6] Remove/replace incorrect references to videobuf
Date: Wed, 10 Aug 2022 15:01:21 +0200	[thread overview]
Message-ID: <20220810130127.2707169-1-hverkuil-cisco@xs4all.nl> (raw)

Quite a few drivers and even the vb2 framework still contain references
to the old videobuf framework, even though they don't use that anymore.

Typically this is either in dead code (ngene), or using the term
videobuf/video-buf when either vb2 or 'video buffer' is meant.

There are also a few functions that use _videobuf_ where _video_buf_
is more appropriate.

This series cleans up the terminology, and this also makes it easier
to identify the remaining drivers that actually use the old videobuf
framework.

No code was changed, it is all comments or renaming functions.

Regards,

	Hans

Hans Verkuil (6):
  media/pci/ngene/ngene.h: remove #ifdef NGENE_V4L
  vb2: videobuf -> videobuf2
  media/v4l2-mem2mem.h: rename 'videobuf' to 'vb2'
  media: platform: ti: avoid using 'videobuf' or 'video-buf'
  staging/media/omap4iss/iss_video.c: videobuf -> vb2
  media: avoid use of 'videobuf'

 .../driver-api/media/drivers/pxa_camera.rst   |  2 +-
 .../media/common/videobuf2/videobuf2-core.c   | 14 ++--
 .../media/common/videobuf2/videobuf2-dvb.c    |  4 +-
 .../media/common/videobuf2/videobuf2-v4l2.c   |  4 +-
 drivers/media/dvb-frontends/rtl2832_sdr.c     |  2 +-
 drivers/media/pci/ngene/ngene.h               | 78 -------------------
 .../media/pci/solo6x10/solo6x10-v4l2-enc.c    |  2 +-
 drivers/media/platform/intel/pxa_camera.c     |  8 +-
 drivers/media/platform/marvell/mcam-core.h    |  2 +-
 .../media/platform/renesas/vsp1/vsp1_video.c  |  2 +-
 .../platform/samsung/exynos4-is/fimc-core.h   |  2 +-
 .../media/platform/samsung/s5p-mfc/s5p_mfc.c  |  2 +-
 .../media/platform/ti/am437x/am437x-vpfe.h    |  2 +-
 drivers/media/platform/ti/davinci/vpif.h      | 60 +++++++-------
 .../media/platform/ti/davinci/vpif_capture.c  |  6 +-
 .../media/platform/ti/davinci/vpif_capture.h  |  2 +-
 .../media/platform/ti/davinci/vpif_display.c  |  6 +-
 .../media/platform/ti/davinci/vpif_display.h  |  6 +-
 drivers/media/platform/ti/omap3isp/ispvideo.c |  2 +-
 drivers/media/test-drivers/vim2m.c            |  2 +-
 drivers/media/usb/airspy/airspy.c             |  2 +-
 drivers/media/usb/au0828/au0828-video.c       |  4 +-
 drivers/media/usb/cx231xx/cx231xx-vbi.c       |  2 +-
 drivers/media/usb/cx231xx/cx231xx-video.c     |  2 +-
 drivers/media/usb/em28xx/em28xx-video.c       |  4 +-
 drivers/media/usb/msi2500/msi2500.c           |  2 +-
 drivers/media/usb/pvrusb2/pvrusb2-dvb.c       |  2 +-
 drivers/media/v4l2-core/v4l2-mem2mem.c        |  6 +-
 drivers/staging/media/omap4iss/iss_video.c    |  2 +-
 include/media/davinci/vpbe_display.h          |  6 +-
 include/media/v4l2-mem2mem.h                  | 12 +--
 include/media/videobuf2-core.h                | 16 ++--
 include/media/videobuf2-dvb.h                 |  2 +-
 33 files changed, 96 insertions(+), 174 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-08-10 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 13:01 Hans Verkuil [this message]
2022-08-10 13:01 ` [PATCH 1/6] media/pci/ngene/ngene.h: remove #ifdef NGENE_V4L Hans Verkuil
2022-08-10 13:01 ` [PATCH 2/6] vb2: videobuf -> videobuf2 Hans Verkuil
2022-08-10 13:01 ` [PATCH 3/6] media/v4l2-mem2mem.h: rename 'videobuf' to 'vb2' Hans Verkuil
2022-08-10 13:01 ` [PATCH 4/6] media: platform: ti: avoid using 'videobuf' or 'video-buf' Hans Verkuil
2022-08-11  9:27   ` Lad, Prabhakar
2022-08-10 13:01 ` [PATCH 5/6] staging/media/omap4iss/iss_video.c: videobuf -> vb2 Hans Verkuil
2022-08-10 13:01 ` [PATCH 6/6] media: avoid use of 'videobuf' 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=20220810130127.2707169-1-hverkuil-cisco@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.