lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131218141656.7dfae8fc@gandalf.local.home>
Date:	Wed, 18 Dec 2013 14:16:56 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Marek <mmarek@...e.cz>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC][PATCH 0/2] localmodconfig / ALSA: hda - Have codecs be
 disabled by localmodconfig

On Wed, 18 Dec 2013 20:05:11 +0100
Takashi Iwai <tiwai@...e.de> wrote:

 
> Well, as mentioned in the mail thread, I'm afraid that people don't
> like to see yet doubled kconfig items just for workarounds by this
> approach.  So it'd be likely better not to restrict but just let users
> choose tristate.  I already submitted the patches (the same ones as
> attached before) to alsa-devel ML.

Sure, that's why I added the RFC.

> 
> Another thing we may add is a warning like:
> 
> ================================================================
> config SND_HDA_CODEC_REALTEK
> 	tristate "Build Realtek HD-audio codec support"
> 	select SND_HDA_GENERIC
> 	help
> 	  Say Y or M here to include Realtek HD-audio codec support in
> 	  snd-hda-intel driver, such as ALC880.
> 
> comment "Set to Y if you want auto-loading the codec driver"
> 	depends on SND_HDA_CODEC_REALTEK && SND_HDA_INTEL != SND_HDA_CODEC_REALTEK
> ================================================================
> 
> The comment won't break make localmodconfig, right?

Nope, it shouldn't affect localmodconfig at all.

> This should be intuitive enough for avoiding pitfalls, I hope.

But the first patch still needs to be added. I'll just send that out by
itself.

Thanks,

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ