linux-kernel - Re: [GIT PULL] sound updates for 3.1-rc1

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 23 Jul 2011 11:06:14 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] sound updates for 3.1-rc1

On Sat, Jul 23, 2011 at 9:32 AM, Takashi Iwai <tiwai@...e.de> wrote:
>
> As you can see below, the diffstat shows awfully huge numbers.  It's
> mainly the reworks of two HD-audio drivers after I finally had some
> spare time and a gut to face them.  Most of LOCs there are due to code
> split, but also a significant amount of code reduction has been done,
> too.  In addition, as usual, many ASoC fixes/updates have been applied
> in this cycle, too.

So wrt that whole HDA thing, can somebody explain what the difference
between a "patch" and a "quirk" is? It looks like the "quirks" are
smaller patches (they all seem to be about realtek, at least
currently).

And does it really make sense to use #include to get the *.c files?
Wouldn't it be much nicer to have a "realtek" subdirectory and link
those together.

I don't care deeply, but the whole HDA source organization is getting
pretty darn ugly, I have to say.

                   Linus
--
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/