From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: deller@gmx.de, kherbst@redhat.com, lyude@redhat.com,
dakr@redhat.com, jani.nikula@linux.intel.com, daniel@ffwll.ch,
airlied@gmail.com, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v2 2/8] staging/fbtft: Include <linux/backlight.h>
Date: Sat, 17 Feb 2024 17:24:42 +0100 [thread overview]
Message-ID: <2024021735-impure-excitable-6266@gregkh> (raw)
In-Reply-To: <20240213084403.20995-3-tzimmermann@suse.de>
On Tue, Feb 13, 2024 at 09:42:20AM +0100, Thomas Zimmermann wrote:
> Resolved the proxy include via <linux/fb.h>, which does not require the
> backlight header.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2024-02-17 16:24 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 [this message]
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 ` [PATCH v2 0/8] fbdev: Clean up include dependencies in header 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=2024021735-impure-excitable-6266@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.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 \
--cc=tzimmermann@suse.de \
/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.