linux-kernel - [PATCH 0/6] staging: line6: drop driver-specific dumping code

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

Date:	Wed, 14 Nov 2012 08:50:40 +0100
From:	Stefan Hajnoczi <stefanha@...il.com>
To:	devel@...verdev.osuosl.org
Cc:	Markus Grabner <grabner@....tugraz.at>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	line6linux-devel@...ts.sourceforge.net,
	<linux-kernel@...r.kernel.org>,
	Stefan Hajnoczi <stefanha@...il.com>
Subject: [PATCH 0/6] staging: line6: drop driver-specific dumping code

The line6 driver has compile-time options for dumping USB and MIDI data.
This functionality has been superceded by usbmon and amidi/aseqdump.
These mechanisms can be enabled at run-time and have other features not
in the line6 dumping code.  Therefore it's time to drop the
driver-specific dumping code as part of the effort to clean up the driver
and get it out of staging.

Stefan Hajnoczi (6):
  staging: line6: drop control URB dumping code
  staging: line6: drop CONTROL from CONFIG_LINE6_USB_DUMP_ANY
  staging: line6: drop unused CONFIG_LINE6_USB_DUMP_CTRL
  staging: line6: drop MIDI dumping code
  staging: line6: drop MIDI from CONFIG_LINE6_USB_DUMP_ANY
  staging: line6: drop unused CONFIG_LINE6_USB_DUMP_MIDI

 drivers/staging/line6/Kconfig  | 18 ------------------
 drivers/staging/line6/driver.c | 39 ---------------------------------------
 drivers/staging/line6/driver.h |  2 +-
 drivers/staging/line6/midi.c   |  6 ------
 4 files changed, 1 insertion(+), 64 deletions(-)

-- 
1.8.0

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