From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Cc: Andy Walls <awalls@md.metrocast.net>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, ivtv-devel@ivtvdriver.org,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 12/14] media: constify fb ops across all drivers
Date: Fri, 29 Nov 2019 10:35:44 +0000 [thread overview]
Message-ID: <87h82nkm0v.fsf@intel.com> (raw)
In-Reply-To: <9cfc1a171d12a52dfbd5508d737681f2d89d21df.1575022735.git.jani.nikula@intel.com>
On Fri, 29 Nov 2019, Jani Nikula <jani.nikula@intel.com> wrote:
> Now that the fbops member of struct fb_info is const, we can start
> making the ops const as well.
>
> Remove the redundant fbops assignments while at it.
>
> v2:
> - actually add const in vivid
> - fix typo (Christophe de Dinechin)
>
> Cc: Hans Verkuil <hverkuil@xs4all.nl>
> Cc: Andy Walls <awalls@md.metrocast.net>
> Cc: linux-media@vger.kernel.org
> Cc: ivtv-devel@ivtvdriver.org
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> fixup-to-media
Rebase artefact, to be removed before applying...
BR,
Jani.
> ---
> drivers/media/pci/ivtv/ivtvfb.c | 3 +--
> drivers/media/platform/vivid/vivid-osd.c | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/media/pci/ivtv/ivtvfb.c b/drivers/media/pci/ivtv/ivtvfb.c
> index 95a56cce9b65..f2922b554b09 100644
> --- a/drivers/media/pci/ivtv/ivtvfb.c
> +++ b/drivers/media/pci/ivtv/ivtvfb.c
> @@ -925,7 +925,7 @@ static int ivtvfb_blank(int blank_mode, struct fb_info *info)
> return 0;
> }
>
> -static struct fb_ops ivtvfb_ops = {
> +static const struct fb_ops ivtvfb_ops = {
> .owner = THIS_MODULE,
> .fb_write = ivtvfb_write,
> .fb_check_var = ivtvfb_check_var,
> @@ -1049,7 +1049,6 @@ static int ivtvfb_init_vidmode(struct ivtv *itv)
>
> oi->ivtvfb_info.node = -1;
> oi->ivtvfb_info.flags = FBINFO_FLAG_DEFAULT;
> - oi->ivtvfb_info.fbops = &ivtvfb_ops;
> oi->ivtvfb_info.par = itv;
> oi->ivtvfb_info.var = oi->ivtvfb_defined;
> oi->ivtvfb_info.fix = oi->ivtvfb_fix;
> diff --git a/drivers/media/platform/vivid/vivid-osd.c b/drivers/media/platform/vivid/vivid-osd.c
> index f2e789bdf4a6..fbaec8acc161 100644
> --- a/drivers/media/platform/vivid/vivid-osd.c
> +++ b/drivers/media/platform/vivid/vivid-osd.c
> @@ -244,7 +244,7 @@ static int vivid_fb_blank(int blank_mode, struct fb_info *info)
> return 0;
> }
>
> -static struct fb_ops vivid_fb_ops = {
> +static const struct fb_ops vivid_fb_ops = {
> .owner = THIS_MODULE,
> .fb_check_var = vivid_fb_check_var,
> .fb_set_par = vivid_fb_set_par,
> @@ -311,7 +311,6 @@ static int vivid_fb_init_vidmode(struct vivid_dev *dev)
>
> dev->fb_info.node = -1;
> dev->fb_info.flags = FBINFO_FLAG_DEFAULT;
> - dev->fb_info.fbops = &vivid_fb_ops;
> dev->fb_info.par = dev;
> dev->fb_info.var = dev->fb_defined;
> dev->fb_info.fix = dev->fb_fix;
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-11-29 10:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 10:29 [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Jani Nikula
2019-11-29 10:29 ` [PATCH v2 01/14] video: fb_defio: preserve user fb_ops Jani Nikula
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 15:22 ` Daniel Vetter
2019-11-29 10:29 ` [PATCH v2 02/14] drm/fb-helper: don't preserve fb_ops across deferred IO use Jani Nikula
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 10:29 ` [PATCH v2 03/14] video: smscufx: don't restore fb_mmap after deferred IO cleanup Jani Nikula
2019-11-29 10:29 ` [PATCH v2 04/14] video: udlfb: " Jani Nikula
2019-11-29 10:29 ` [PATCH v2 05/14] video: fbdev: vesafb: modify the static fb_ops directly Jani Nikula
2019-11-29 10:29 ` [PATCH v2 06/14] video: fbmem: use const pointer for fb_ops Jani Nikula
2019-11-29 15:25 ` [Intel-gfx] " Daniel Vetter
2019-11-29 10:29 ` [PATCH v2 07/14] video: omapfb: " Jani Nikula
2019-12-03 9:16 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 08/14] video: fbdev: make fbops member of struct fb_info a const pointer Jani Nikula
2019-11-30 1:41 ` kbuild test robot
2019-11-29 10:29 ` [PATCH v2 09/14] drm: constify fb ops across all drivers Jani Nikula
2019-11-29 10:29 ` [PATCH v2 10/14] video: " Jani Nikula
2019-11-29 10:35 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` [PATCH v2 11/14] HID: picoLCD: constify fb ops Jani Nikula
2019-12-02 8:40 ` Bruno Prémont
2019-12-05 9:38 ` Jani Nikula
2019-12-08 0:07 ` Jiri Kosina
2019-11-29 10:29 ` [PATCH v2 12/14] media: constify fb ops across all drivers Jani Nikula
2019-11-29 10:35 ` Jani Nikula [this message]
2019-11-29 10:29 ` [PATCH v2 13/14] samples: vfio-mdev: constify fb ops Jani Nikula
2019-11-29 10:29 ` [PATCH v2 14/14] auxdisplay: " Jani Nikula
2019-11-29 15:24 ` Daniel Vetter
2019-11-29 20:16 ` Miguel Ojeda
2019-11-29 20:30 ` Daniel Vetter
2019-11-29 20:59 ` Miguel Ojeda
2019-12-02 8:08 ` robin
2019-12-02 7:37 ` robin
2019-11-29 15:40 ` [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Daniel Vetter
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=87h82nkm0v.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=awalls@md.metrocast.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ivtv-devel@ivtvdriver.org \
--cc=linux-fbdev@vger.kernel.org \
--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).