From: Hans de Goede <hdegoede@redhat.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Tsuchiya Yuto <kitakar@gmail.com>,
Andy Shevchenko <andy@kernel.org>,
Yury Luneff <yury.lunev@gmail.com>,
Nable <nable.maininbox@googlemail.com>,
andrey.i.trufanov@gmail.com, Fabio Aiuto <fabioaiuto83@gmail.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [PATCH 00/14] media: atomisp: More cleanups / code removal
Date: Thu, 1 Sep 2022 11:46:12 +0200 [thread overview]
Message-ID: <20220901094626.11513-1-hdegoede@redhat.com> (raw)
Hi Mauro,
Here is a second set of atomisp cleanups / code removal.
This applies on top of my previous v2 series from here:
https://lore.kernel.org/linux-media/20220822150610.45186-1-hdegoede@redhat.com/
I plan to do more atomisp work the coming few weeks. So I'm thinking
it might be better / easier for you if I just send you a pull-req based
on 6.0-rc1 with all atomisp patches bundled around rc5/rc6 time.
Would that work for you ?
I do plan to keep sending out (incremental) patch-sets with my work
(like this one) for review / comments.
Regards,
Hans
Dan Carpenter (1):
media: atomisp: prevent integer overflow in sh_css_set_black_frame()
Hans de Goede (13):
media: atomisp: Fix device_caps reporting of the registered video-devs
media: atomisp: Remove file-injection support
media: atomisp: Remove atomisp_file_fops and atomisp_file_ioctl_ops
media: atomisp: Remove the outq videobuf queue
media: atomisp: Remove never set file_input flag
media: atomisp: Remove the ACC device node
media: atomisp: Remove some further ATOMISP_ACC_* related dead code
media: atomisp: Remove empty atomisp_css_set_cont_prev_start_time()
function
media: atomisp: Split subdev and video-node registration into 2 steps
media: atomisp: Register /dev/* nodes at the end of
atomisp_pci_probe()
media: atomisp: Remove loading mutex
media: atomisp: Fix v4l2_fh resource leak on open errors
media: atomisp: Simplify v4l2_fh_open() error handling
drivers/staging/media/atomisp/Makefile | 1 -
.../media/atomisp/include/linux/atomisp.h | 14 --
.../staging/media/atomisp/pci/atomisp_cmd.c | 134 +---------
.../staging/media/atomisp/pci/atomisp_cmd.h | 2 -
.../media/atomisp/pci/atomisp_compat.h | 6 -
.../media/atomisp/pci/atomisp_compat_css20.c | 26 --
.../staging/media/atomisp/pci/atomisp_file.c | 229 ------------------
.../staging/media/atomisp/pci/atomisp_file.h | 44 ----
.../staging/media/atomisp/pci/atomisp_fops.c | 187 ++------------
.../media/atomisp/pci/atomisp_internal.h | 16 +-
.../staging/media/atomisp/pci/atomisp_ioctl.c | 192 ++-------------
.../staging/media/atomisp/pci/atomisp_ioctl.h | 4 -
.../media/atomisp/pci/atomisp_subdev.c | 95 ++------
.../media/atomisp/pci/atomisp_subdev.h | 47 +---
.../staging/media/atomisp/pci/atomisp_v4l2.c | 99 +++-----
.../staging/media/atomisp/pci/atomisp_v4l2.h | 3 -
.../staging/media/atomisp/pci/sh_css_params.c | 4 +-
17 files changed, 104 insertions(+), 999 deletions(-)
delete mode 100644 drivers/staging/media/atomisp/pci/atomisp_file.c
delete mode 100644 drivers/staging/media/atomisp/pci/atomisp_file.h
--
2.37.2
next reply other threads:[~2022-09-01 9:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 9:46 Hans de Goede [this message]
2022-09-01 9:46 ` [PATCH 01/14] media: atomisp: Fix device_caps reporting of the registered video-devs Hans de Goede
2022-09-01 9:46 ` [PATCH 02/14] media: atomisp: Remove file-injection support Hans de Goede
2022-09-01 9:46 ` [PATCH 03/14] media: atomisp: Remove atomisp_file_fops and atomisp_file_ioctl_ops Hans de Goede
2022-09-01 9:46 ` [PATCH 04/14] media: atomisp: Remove the outq videobuf queue Hans de Goede
2022-09-01 9:46 ` [PATCH 05/14] media: atomisp: Remove never set file_input flag Hans de Goede
2022-09-01 9:46 ` [PATCH 06/14] media: atomisp: Remove the ACC device node Hans de Goede
2022-09-01 9:46 ` [PATCH 07/14] media: atomisp: Remove some further ATOMISP_ACC_* related dead code Hans de Goede
2022-09-01 9:46 ` [PATCH 08/14] media: atomisp: Remove empty atomisp_css_set_cont_prev_start_time() function Hans de Goede
2022-09-01 9:46 ` [PATCH 09/14] media: atomisp: Split subdev and video-node registration into 2 steps Hans de Goede
2022-09-01 9:46 ` [PATCH 10/14] media: atomisp: Register /dev/* nodes at the end of atomisp_pci_probe() Hans de Goede
2022-09-01 19:56 ` Andy Shevchenko
2022-09-02 9:04 ` Hans de Goede
2022-09-02 9:10 ` Andy Shevchenko
2022-09-02 9:16 ` Andy Shevchenko
2022-09-01 9:46 ` [PATCH 11/14] media: atomisp: Remove loading mutex Hans de Goede
2022-09-01 9:46 ` [PATCH 12/14] media: atomisp: Fix v4l2_fh resource leak on open errors Hans de Goede
2022-09-01 9:46 ` [PATCH 13/14] media: atomisp: Simplify v4l2_fh_open() error handling Hans de Goede
2022-09-01 9:46 ` [PATCH 14/14] media: atomisp: prevent integer overflow in sh_css_set_black_frame() Hans de Goede
2022-09-01 15:08 ` [PATCH 00/14] media: atomisp: More cleanups / code removal Mauro Carvalho Chehab
2022-09-01 15:30 ` Hans de Goede
2022-09-01 19:59 ` Andy Shevchenko
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=20220901094626.11513-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=andrey.i.trufanov@gmail.com \
--cc=andy@kernel.org \
--cc=fabioaiuto83@gmail.com \
--cc=kitakar@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=nable.maininbox@googlemail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=yury.lunev@gmail.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 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.