From: Adrian Bunk <bunk@stusta.de>
To: greg@kroah.com, perex@suse.cz
Cc: alsa-devel@alsa-project.org,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] usbusx2yaudio.c: remove an unused variable
Date: Sun, 30 Jan 2005 14:03:14 +0100 [thread overview]
Message-ID: <20050130130314.GL3185@stusta.de> (raw)
In 2.6.11-rc a completely unused variable was added, resulting in the
following compile warning:
<-- snip -->
...
CC sound/usb/usx2y/usx2yhwdeppcm.o
In file included from sound/usb/usx2y/usx2yhwdeppcm.c:53:
sound/usb/usx2y/usbusx2yaudio.c: In function `usX2Y_urbs_allocate':
sound/usb/usx2y/usbusx2yaudio.c:418: warning: unused variable `ep'
...
<-- snip -->
This patch removes this unused variable.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.11-rc2-mm2-full/sound/usb/usx2y/usbusx2yaudio.c.old 2005-01-30 12:26:58.000000000 +0100
+++ linux-2.6.11-rc2-mm2-full/sound/usb/usx2y/usbusx2yaudio.c 2005-01-30 12:27:03.000000000 +0100
@@ -415,7 +415,6 @@
unsigned int pipe;
int is_playback = subs == subs->usX2Y->subs[SNDRV_PCM_STREAM_PLAYBACK];
struct usb_device *dev = subs->usX2Y->chip.dev;
- struct usb_host_endpoint *ep;
pipe = is_playback ? usb_sndisocpipe(dev, subs->endpoint) :
usb_rcvisocpipe(dev, subs->endpoint);
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: greg@kroah.com, perex@suse.cz
Cc: alsa-devel@alsa-project.org,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] usbusx2yaudio.c: remove an unused variable
Date: Sun, 30 Jan 2005 14:03:14 +0100 [thread overview]
Message-ID: <20050130130314.GL3185@stusta.de> (raw)
In 2.6.11-rc a completely unused variable was added, resulting in the
following compile warning:
<-- snip -->
...
CC sound/usb/usx2y/usx2yhwdeppcm.o
In file included from sound/usb/usx2y/usx2yhwdeppcm.c:53:
sound/usb/usx2y/usbusx2yaudio.c: In function `usX2Y_urbs_allocate':
sound/usb/usx2y/usbusx2yaudio.c:418: warning: unused variable `ep'
...
<-- snip -->
This patch removes this unused variable.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.11-rc2-mm2-full/sound/usb/usx2y/usbusx2yaudio.c.old 2005-01-30 12:26:58.000000000 +0100
+++ linux-2.6.11-rc2-mm2-full/sound/usb/usx2y/usbusx2yaudio.c 2005-01-30 12:27:03.000000000 +0100
@@ -415,7 +415,6 @@
unsigned int pipe;
int is_playback = subs == subs->usX2Y->subs[SNDRV_PCM_STREAM_PLAYBACK];
struct usb_device *dev = subs->usX2Y->chip.dev;
- struct usb_host_endpoint *ep;
pipe = is_playback ? usb_sndisocpipe(dev, subs->endpoint) :
usb_rcvisocpipe(dev, subs->endpoint);
next reply other threads:[~2005-01-30 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 13:03 Adrian Bunk [this message]
2005-01-30 13:03 ` [2.6 patch] usbusx2yaudio.c: remove an unused variable Adrian Bunk
2005-01-31 13:44 ` Takashi Iwai
2005-01-31 13:44 ` [Alsa-devel] " Takashi Iwai
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=20050130130314.GL3185@stusta.de \
--to=bunk@stusta.de \
--cc=alsa-devel@alsa-project.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.