linux-kernel - Re: [PATCH 00/25] line6usb cleanup

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

Message-ID: <CAJSP0QVc2VkxNZ0AOx+LQZ=_z_bYEfEVvYQ0tnCbfP6FvErFsw@mail.gmail.com>
Date:	Sun, 11 Jan 2015 11:26:12 +0000
From:	Stefan Hajnoczi <stefanha@...il.com>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Chris Rorvick <chris@...vick.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Alexey Khoroshilov <khoroshilov@...ras.ru>,
	Davide Berardi <berardi.dav@...il.com>,
	devel@...verdev.osuosl.org,
	Fabian Mewes <architekt@...ing4coffee.org>,
	Gulsah Kose <gulsah.1004@...il.com>,
	Himangi Saraogi <himangi774@...il.com>,
	Jerry Snitselaar <dev@...tselaar.org>,
	L. Alberto Giménez <agimenez@...valve.es>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Mikhail Boiko <mm.boiko@...dex.ru>,
	Monam Agarwal <monamagarwal123@...il.com>,
	Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
Subject: Re: [PATCH 00/25] line6usb cleanup

On Sun, Jan 11, 2015 at 10:34 AM, Takashi Iwai <tiwai@...e.de> wrote:
> At Fri,  9 Jan 2015 23:35:46 -0600,
> Chris Rorvick wrote:
>>
>> The line6usb driver references the device's idProduct and, in some
>> cases, the interface number in a number of places to determine device-
>> specific configuration values and to call device-specific functionality.
>> Rework code to leverage the device table matching more effectively.
>> Consolidate configuration settings into the properties entries and use
>> function pointers setup at initialization to remove much of the
>> conditional logic.
>>
>> I have a TonePort UX2 that I've used for testing, meaning that some of
>> this is really only compile-tested.
>
> BTW, are there any active developers for this driver?  It doesn't make
> sense to sit in staging directory forever.  It should be promoted to
> the official sound directory, or dropped from the kernel tree if not.
> If anyone is responsible for testing with real hardware, I'll happily
> review.

I am not active but willing to help with review and advice if anyone
wants to tackle this driver.

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