From: Thomas Zimmermann <tzimmermann@suse.de>
To: deller@gmx.de, kherbst@redhat.com, lyude@redhat.com,
dakr@redhat.com, jani.nikula@linux.intel.com, daniel@ffwll.ch,
airlied@gmail.com, gregkh@linuxfoundation.org
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org, linux-staging@lists.linux.dev,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH v3 0/9] fbdev: Clean up include dependencies in header
Date: Mon, 19 Feb 2024 10:37:25 +0100 [thread overview]
Message-ID: <20240219093941.3684-1-tzimmermann@suse.de> (raw)
Remove unnecessary dependencies in the include statements of the
header file <linux/fb.h>. Several files throughout the kernel include
the fbdev header, so reducing dependencies positively affects other
subsystems as well. Also fix up corgi-lcd, nouveau and fbtft, which
need backlight.h in some of their source files.
v3:
* include backlight.h in corgi-lcd (kernel test robot)
* grammar fixes in commit messages
v2:
* include backlight.h in fbtft (kernel test robot)
Thomas Zimmermann (9):
backlight/corgi-lcd: Include <linux/backlight.h>
drm/nouveau: Include <linux/backlight.h>
staging/fbtft: Include <linux/backlight.h>
fbdev: Do not include <linux/backlight.h> in header
fbdev: Do not include <linux/fs.h> in header
fbdev: Do not include <linux/notifier.h> in header
fbdev: Do not include <linux/slab.h> in header
fbdev: Clean up forward declarations in header file
fbdev: Clean up include statements in header file
drivers/gpu/drm/nouveau/dispnv50/disp.c | 1 +
drivers/staging/fbtft/fb_ssd1351.c | 2 ++
drivers/video/backlight/corgi_lcd.c | 1 +
include/linux/fb.h | 24 +++++++++++++-----------
4 files changed, 17 insertions(+), 11 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-19 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:37 Thomas Zimmermann [this message]
2024-02-19 9:37 ` [PATCH v3 1/9] backlight/corgi-lcd: Include <linux/backlight.h> Thomas Zimmermann
2024-02-21 10:29 ` Thomas Zimmermann
2024-02-23 10:56 ` Lee Jones
2024-02-26 11:42 ` Jani Nikula
2024-02-26 12:33 ` Lee Jones
2024-02-26 12:48 ` Thomas Zimmermann
2024-02-26 12:52 ` Lee Jones
2024-02-19 9:37 ` [PATCH v3 2/9] drm/nouveau: " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 3/9] staging/fbtft: " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 4/9] fbdev: Do not include <linux/backlight.h> in header Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 5/9] fbdev: Do not include <linux/fs.h> " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 6/9] fbdev: Do not include <linux/notifier.h> " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 7/9] fbdev: Do not include <linux/slab.h> " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 8/9] fbdev: Clean up forward declarations in header file Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 9/9] fbdev: Clean up include statements " Thomas Zimmermann
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=20240219093941.3684-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=kherbst@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.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 read-only IMAP folder(s) and NNTP newsgroup(s).