From: Daniel Mack <daniel@caiaq.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH] ALSA: usb/mixer.c: remove unused variable
Date: Thu, 20 May 2010 01:41:09 +0200 [thread overview]
Message-ID: <20100519234109.GY30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <s5hr5l76eiu.wl%tiwai@suse.de>
On Wed, May 19, 2010 at 06:29:45PM +0200, Takashi Iwai wrote:
> At Wed, 19 May 2010 17:34:45 +0200,
> Daniel Mack wrote:
> >
> > This was a development left-over.
> >
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Cc: Takashi Iwai <tiwai@suse.de>
> > Cc: Clemens Ladisch <clemens@ladisch.de>
>
> This can't be applied to the latest tree. Missing patches?
Gna, I've been working on a wrong branch, sorry. Please drop this patch.
Daniel
next prev parent reply other threads:[~2010-05-19 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 15:34 [PATCH] ALSA: usb/mixer.c: remove unused variable Daniel Mack
2010-05-19 16:29 ` Takashi Iwai
2010-05-19 23:41 ` Daniel Mack [this message]
2010-05-30 22:12 ` Mute LED on HP Pavilion DV7-1160eg Thoralf Freitag
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=20100519234109.GY30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).