From: Adam Goode <agoode@google.com>
To: patch@alsa-project.org
Cc: alsa-devel@alsa-project.org
Subject: [PATCH v2 - sound/usb 0/2] Respond to suspend and resume callbacks for usb midi
Date: Tue, 5 Aug 2014 12:44:49 -0400 [thread overview]
Message-ID: <1407257091-16462-1-git-send-email-agoode@google.com> (raw)
In-Reply-To: <s5hegwv6rl8.wl%tiwai@suse.de>
Hi Takashi,
This is v2 of the midi input fix. I still need to work on fixing output in the same way,
though it is less serious.
I have a whitespace cleanup patch as well, feel free to ignore.
Thanks,
Adam
next prev parent reply other threads:[~2014-08-05 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 12:20 [PATCH - sound/usb 1/1] Respond to suspend and resume callbacks for input in sound/usb/midi.c Adam Goode
2014-08-05 12:36 ` Takashi Iwai
2014-08-05 16:44 ` Adam Goode [this message]
2014-08-05 16:44 ` [PATCH v2 - sound/usb 1/2] Respond to suspend and resume callbacks for MIDI input in sound/usb Adam Goode
2014-08-05 16:44 ` [PATCH v2 - sound/usb 2/2] Whitespace cleanups for sound/usb/midi.* Adam Goode
2014-08-05 18:09 ` [PATCH v2 - sound/usb 0/2] Respond to suspend and resume callbacks for usb midi 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=1407257091-16462-1-git-send-email-agoode@google.com \
--to=agoode@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=patch@alsa-project.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;
as well as URLs for NNTP newsgroup(s).