From: Randy Dunlap <rdunlap@infradead.org>
To: Udo van den Heuvel <udovdh@xs4all.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-leds@vger.kernel.org, Dan Murphy <dmurphy@ti.com>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: disabling CONFIG_LED_CLASS
Date: Tue, 13 Oct 2020 21:49:29 -0700 [thread overview]
Message-ID: <27e159be-4376-e87b-5e60-803bc3749ec2@infradead.org> (raw)
In-Reply-To: <9fc679e9-e9a9-ad80-b24c-f04489b98aa7@xs4all.nl>
On 10/13/20 9:39 PM, Udo van den Heuvel wrote:
> On 14-10-2020 06:34, Randy Dunlap wrote:
>> On 10/13/20 9:29 PM, Udo van den Heuvel wrote:
>>> So we still are stuck.
>
> (...)
>
>
>> Please post your .config file.
>
> Attached to this message.
> This is the version stripped from LED references.
This is the problem:
config SND_HDA_CODEC_REALTEK
tristate "Build Realtek HD-audio codec support"
select SND_HDA_GENERIC
select SND_HDA_GENERIC_LEDS
If you disable SND_HDA_CODEC_REALTEK, then the rest of the
LED kconfig symbols can be disabled.
lnx-59> grep LEDS xx64/.config
# CONFIG_NEW_LEDS is not set
--
~Randy
next prev parent reply other threads:[~2020-10-14 8:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2835d02a-380b-6a3a-0e4d-abf07aee18bc@xs4all.nl>
[not found] ` <53e698c1-86e4-8b1f-afb0-b8471349e701@xs4all.nl>
2020-10-13 15:53 ` disabling CONFIG_LED_CLASS Randy Dunlap
2020-10-13 16:03 ` Randy Dunlap
2020-10-14 4:29 ` Udo van den Heuvel
2020-10-14 4:34 ` Randy Dunlap
[not found] ` <9fc679e9-e9a9-ad80-b24c-f04489b98aa7@xs4all.nl>
2020-10-14 4:49 ` Randy Dunlap [this message]
2020-10-14 4:56 ` Udo van den Heuvel
2020-10-14 5:07 ` Randy Dunlap
2020-10-14 5:16 ` Udo van den Heuvel
2020-10-14 5:54 ` disabling CONFIG_LED_CLASS (SND_HDA_CODEC_REALTEK) Randy Dunlap
2020-10-14 7:49 ` Takashi Iwai
2020-10-14 7:51 ` Takashi Iwai
2020-10-14 7:58 ` Pavel Machek
2020-10-14 8:05 ` Udo van den Heuvel
2020-10-14 8:11 ` Pavel Machek
2020-10-14 8:22 ` Udo van den Heuvel
2020-10-14 8:27 ` Pavel Machek
2020-10-14 8:34 ` Udo van den Heuvel
2020-10-14 8:37 ` Pavel Machek
2020-10-19 8:35 ` Udo van den Heuvel
2020-10-19 10:58 ` Marek Behún
2020-10-14 8:06 ` Takashi Iwai
2020-10-14 7:54 ` Pavel Machek
2020-10-14 8:08 ` Takashi Iwai
2020-10-14 8:13 ` Pavel Machek
2020-10-14 8:17 ` Takashi Iwai
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=27e159be-4376-e87b-5e60-803bc3749ec2@infradead.org \
--to=rdunlap@infradead.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=udovdh@xs4all.nl \
/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).