From: Robin van der Gracht <robin@protonic.nl>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
Sean Paul <seanpaul@chromium.org>,
Greg Kroah-Hartman <gregkh@google.com>,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [char-misc:char-misc-testing] warning
Date: Wed, 2 Nov 2016 08:23:52 +0100 [thread overview]
Message-ID: <20161102082352.4dd8bed5@erd979> (raw)
In-Reply-To: <9b957180-340e-51a6-bbee-01353de79925@infradead.org>
Hi Randy,
On Tue, 1 Nov 2016 09:34:04 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 11/01/16 09:02, Robin van der Gracht wrote:
> > Hi Tobias,
> >
> > On Tue, 1 Nov 2016 16:33:03 +0100
> > Tobias Jakobi <tjakobi@math.uni-bielefeld.de> wrote:
> >
> >> Hello Robin,
> >>
> >> I'm afraid I can't help you with that. The series was done as a request
> >> by Daniel Vetter, see here for reference:
> >> http://www.spinics.net/lists/dri-devel/msg113011.html
> > So.. I should contact Daniel Vetter about this..?
> >
> >> I don't have any nouveau platform here.
> >
> > Me neither, the warning is shown when invoking Kconfig. So when I use
> > the config file supplied on my previous email, and start a build or a
> > menuconfig on my (x86_64) system its showing.
>
>
> The kconfig warning is in mainline now and it has nothing to do with the
> new HT16K33 driver.
>
> How is nouveau supposed to provide backlight support?
> It selects FB_BACKLIGHT but FB_BACKLIGHT depends on FB, which is not
> enabled in the supplied .config file.
Yes, exactly!
I think that line should have been removed along with the other FB deps.
Regards,
--
Robin van der Gracht
Protonic Holland
prev parent reply other threads:[~2016-11-02 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 14:07 [char-misc:char-misc-testing] warning Robin van der Gracht
2016-11-01 15:33 ` Tobias Jakobi
2016-11-01 16:02 ` Robin van der Gracht
2016-11-01 16:34 ` Randy Dunlap
2016-11-02 7:23 ` Robin van der Gracht [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=20161102082352.4dd8bed5@erd979 \
--to=robin@protonic.nl \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=seanpaul@chromium.org \
--cc=tjakobi@math.uni-bielefeld.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