From: Arnd Bergmann <arnd@kernel.org>
To: Karol Herbst <kherbst@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>, David Airlie <airlied@linux.ie>,
nouveau <nouveau@lists.freedesktop.org>,
Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Nikola Cornij <nikola.cornij@amd.com>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH] drm/nouveau/kms/nv50-: fix build failure with CONFIG_BACKLIGHT=n
Date: Fri, 23 Jul 2021 20:40:19 +0200 [thread overview]
Message-ID: <CAK8P3a0YiAgTLptmPbK6vczkMi7F=tzE-Ae8GPFnBtbvQnoF0Q@mail.gmail.com> (raw)
In-Reply-To: <CACO55ttjQO5kUeEA7opvGLAwT+a1t0vAguncKDhB4bdy96K7LA@mail.gmail.com>
On Fri, Jul 23, 2021 at 6:34 PM Karol Herbst <kherbst@redhat.com> wrote:
> On Fri, Jul 23, 2021 at 6:31 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> > On 7/23/21 8:15 AM, Karol Herbst wrote:
> > > On Fri, Jul 23, 2021 at 5:10 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> > >
> > > what's actually the use case of compiling with
> > > CONFIG_DRM_NOUVEAU_BACKLIGHT=n anyway?
> >
> > Dunno. In this case it was just a randconfig. Still, it needs to be
> > handled in some way - such as the other suggestion in this thread.
> >
>
> sure, I was just curious if there was a specific use case or just
> something random as you mentioned.
I think this is purely done because of tradition. A long time ago, we had
tiny framebuffer drivers and most PCs did not have backlights, so it
made sense to leave this optional.
This was probably just always carried over.
Arnd
next prev parent reply other threads:[~2021-07-23 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 9:15 [PATCH] drm/nouveau/kms/nv50-: fix build failure with CONFIG_BACKLIGHT=n Arnd Bergmann
2021-07-23 9:24 ` Daniel Vetter
2021-07-23 10:10 ` Karol Herbst
2021-07-23 10:12 ` Karol Herbst
2021-07-23 10:16 ` Arnd Bergmann
2021-07-23 15:23 ` Daniel Vetter
2021-07-23 19:14 ` Cornij, Nikola
2021-07-23 19:54 ` Harry Wentland
2021-07-23 16:12 ` Lyude Paul
2021-07-23 15:10 ` Randy Dunlap
2021-07-23 15:15 ` Karol Herbst
2021-07-23 16:31 ` Randy Dunlap
2021-07-23 16:34 ` Karol Herbst
2021-07-23 18:40 ` Arnd Bergmann [this message]
2021-07-23 18:48 ` Karol Herbst
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='CAK8P3a0YiAgTLptmPbK6vczkMi7F=tzE-Ae8GPFnBtbvQnoF0Q@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikola.cornij@amd.com \
--cc=nouveau@lists.freedesktop.org \
--cc=rdunlap@infradead.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).