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
Subject: Re: [PATCH v2 0/8] fbdev: Clean up include dependencies in header
Date: Mon, 19 Feb 2024 10:31:01 +0100 [thread overview]
Message-ID: <4c25b689-ab92-4e84-b54c-e80f511e10c7@suse.de> (raw)
In-Reply-To: <20240213084403.20995-1-tzimmermann@suse.de>
A-b'd by Helge via email
Acked-by: Helge Deller <deller@gmx.de>
Am 13.02.24 um 09:42 schrieb Thomas Zimmermann:
> 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 nouveau and fbtft, which need backlight.h
> in some their source files.
>
> v2:
> * include backlight.h in fbtft (kernel test robot)
>
> Thomas Zimmermann (8):
> 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 ++
> include/linux/fb.h | 24 +++++++++++++-----------
> 3 files changed, 16 insertions(+), 11 deletions(-)
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
prev parent reply other threads:[~2024-02-19 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:42 [PATCH v2 0/8] fbdev: Clean up include dependencies in header Thomas Zimmermann
2024-02-13 8:42 ` [PATCH v2 1/8] drm/nouveau: Include <linux/backlight.h> Thomas Zimmermann
2024-02-13 8:42 ` [PATCH v2 2/8] staging/fbtft: " Thomas Zimmermann
2024-02-14 16:29 ` Thomas Zimmermann
2024-02-17 16:24 ` Greg KH
2024-02-13 8:42 ` [PATCH v2 3/8] fbdev: Do not include <linux/backlight.h> in header Thomas Zimmermann
2024-02-18 5:46 ` kernel test robot
2024-02-18 18:22 ` kernel test robot
2024-02-13 8:42 ` [PATCH v2 4/8] fbdev: Do not include <linux/fs.h> " Thomas Zimmermann
2024-02-13 8:42 ` [PATCH v2 5/8] fbdev: Do not include <linux/notifier.h> " Thomas Zimmermann
2024-02-13 8:42 ` [PATCH v2 6/8] fbdev: Do not include <linux/slab.h> " Thomas Zimmermann
2024-02-13 8:42 ` [PATCH v2 7/8] fbdev: Clean up forward declarations in header file Thomas Zimmermann
2024-02-13 8:42 ` [PATCH v2 8/8] fbdev: Clean up include statements " Thomas Zimmermann
2024-02-19 9:31 ` Thomas Zimmermann [this message]
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=4c25b689-ab92-4e84-b54c-e80f511e10c7@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 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.