From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: [alsa-devel] [0/2] Jack reporting
Date: Sun, 20 Jul 2008 20:30:17 +0100 [thread overview]
Message-ID: <20080720193015.GC6719@sirena.org.uk> (raw)
In-Reply-To: <s5hzlocd1g1.wl%tiwai@suse.de>
On Sun, Jul 20, 2008 at 05:23:26PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > Takashi, what's the best way to handle the ALSA bits? The first patch
> > doesn't depend on the new switch type so could be applied as-is but the
> > second (adding the microphone switch type) depends on the input switch
> > type being added - should I resubmit that when the switch type has been
> > merged?
> Yes, please. We need also some consensus how to handle these patches
> covering both areas.
OK, I'll add all the bits that apply to my patch queue for you.
Hopefully we shouldn't find too many changes that need to touch both
sides of things. For those that do hopefully we can do something
similar to what we do with ARM and agree to merge both via one of the
trees.
> BTW, I'll be on vacation for the next week, so the reply will be
> delayed.
Enjoy your holiday!
prev parent reply other threads:[~2008-07-20 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 9:50 [0/2] Jack reporting Mark Brown
2008-07-03 9:52 ` [PATCH 1/2] Add jack reporting API for ALSA Mark Brown
2008-07-03 9:52 ` [PATCH 2/2] Add microphone and headset reporting Mark Brown
2008-07-14 15:11 ` [0/2] Jack reporting Mark Brown
2008-07-16 11:02 ` [alsa-devel] " Takashi Iwai
2008-07-16 12:50 ` Mark Brown
2008-07-16 16:36 ` [alsa-devel] " Dmitry Torokhov
2008-07-17 10:31 ` Mark Brown
2008-07-20 5:23 ` Dmitry Torokhov
2008-07-20 12:17 ` Mark Brown
2008-07-20 15:23 ` Takashi Iwai
2008-07-20 19:30 ` Mark Brown [this message]
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=20080720193015.GC6719@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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).