From: Stefan Hajnoczi <stefanha@gmail.com>
To: devel@driverdev.osuosl.org
Cc: Markus Grabner <grabner@icg.tugraz.at>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
line6linux-devel@lists.sourceforge.net,
<linux-kernel@vger.kernel.org>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: [PATCH 3/6] staging: line6: drop unused CONFIG_LINE6_USB_DUMP_CTRL
Date: Wed, 14 Nov 2012 08:50:43 +0100 [thread overview]
Message-ID: <1352879446-23195-4-git-send-email-stefanha@gmail.com> (raw)
In-Reply-To: <1352879446-23195-1-git-send-email-stefanha@gmail.com>
Signed-off-by: Stefan Hajnoczi <stefanha@gmail.com>
---
drivers/staging/line6/Kconfig | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/drivers/staging/line6/Kconfig b/drivers/staging/line6/Kconfig
index a5ded12..2101799 100644
--- a/drivers/staging/line6/Kconfig
+++ b/drivers/staging/line6/Kconfig
@@ -23,15 +23,6 @@ menuconfig LINE6_USB
if LINE6_USB
-config LINE6_USB_DUMP_CTRL
- bool "dump control messages"
- default n
- help
- Say Y here to write control messages sent to and received from
- Line6 devices to the syslog.
-
- If unsure, say N.
-
config LINE6_USB_DUMP_MIDI
bool "dump MIDI messages"
default n
--
1.8.0
next prev parent reply other threads:[~2012-11-14 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 7:50 [PATCH 0/6] staging: line6: drop driver-specific dumping code Stefan Hajnoczi
2012-11-14 7:50 ` [PATCH 1/6] staging: line6: drop control URB " Stefan Hajnoczi
2012-11-14 7:50 ` [PATCH 2/6] staging: line6: drop CONTROL from CONFIG_LINE6_USB_DUMP_ANY Stefan Hajnoczi
2012-11-14 7:50 ` Stefan Hajnoczi [this message]
2012-11-14 7:50 ` [PATCH 4/6] staging: line6: drop MIDI dumping code Stefan Hajnoczi
2012-11-14 7:50 ` [PATCH 5/6] staging: line6: drop MIDI from CONFIG_LINE6_USB_DUMP_ANY Stefan Hajnoczi
2012-11-14 7:50 ` [PATCH 6/6] staging: line6: drop unused CONFIG_LINE6_USB_DUMP_MIDI Stefan Hajnoczi
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=1352879446-23195-4-git-send-email-stefanha@gmail.com \
--to=stefanha@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=grabner@icg.tugraz.at \
--cc=gregkh@linuxfoundation.org \
--cc=line6linux-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome