From: Randy Dunlap <rdunlap@infradead.org>
To: Arnd Bergmann <arnd@kernel.org>, dri-devel@lists.freedesktop.org
Cc: linux-fbdev@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Jens Frederich <jfrederich@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-staging@lists.linux.dev,
Lars Poeschel <poeschel@lemonage.de>,
linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>,
Robin van der Gracht <robin@protonic.nl>,
linuxppc-dev@lists.ozlabs.org,
Jon Nettleton <jon.nettleton@gmail.com>
Subject: Re: [PATCH 2/3] fbdev: rework backlight dependencies
Date: Wed, 27 Oct 2021 12:25:47 -0700 [thread overview]
Message-ID: <e19f3eeb-e1c4-ff0e-cf97-f98bd420f842@infradead.org> (raw)
In-Reply-To: <20211027132732.3993279-2-arnd@kernel.org>
On 10/27/21 6:27 AM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Rather than having CONFIG_FB_BACKLIGHT select CONFIG_BACKLIGHT_CLASS_DEVICE,
> make any driver that needs it have a dependency on the class device
> being available, to prevent circular dependencies.
>
> This is the same way that the backlight is already treated for the DRM
> subsystem.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/auxdisplay/Kconfig | 1 +
> drivers/macintosh/Kconfig | 1 +
> drivers/staging/fbtft/Kconfig | 1 +
> drivers/staging/olpc_dcon/Kconfig | 2 +-
> drivers/video/fbdev/Kconfig | 14 +++++++++++---
> 5 files changed, 15 insertions(+), 4 deletions(-)
Acked-by: Randy Dunlap <rdunlap@infraded.org>
Thanks.
--
~Randy
prev parent reply other threads:[~2021-10-27 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211027132732.3993279-1-arnd@kernel.org>
2021-10-27 13:27 ` [PATCH 2/3] fbdev: rework backlight dependencies Arnd Bergmann
2021-10-27 13:32 ` Miguel Ojeda
2021-10-27 19:25 ` Randy Dunlap [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=e19f3eeb-e1c4-ff0e-cf97-f98bd420f842@infradead.org \
--to=rdunlap@infradead.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jfrederich@gmail.com \
--cc=jon.nettleton@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ojeda@kernel.org \
--cc=poeschel@lemonage.de \
--cc=robin@protonic.nl \
--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 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).