From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/3] sound card dir under debugfs
Date: Fri, 5 Nov 2010 14:46:03 -0400 [thread overview]
Message-ID: <20101105184603.GC9139@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101105204146.387fc095.jhnikula@gmail.com>
On Fri, Nov 05, 2010 at 08:41:46PM +0200, Jarkko Nikula wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> > Please resubmit the stuff you're depending on.
> Only dependency is this which got applied as far as I got it:
> http://mailman.alsa-project.org/pipermail/alsa-devel/2010-November/033419.html
Oh, in which case there's no need to note the dependency since it's
already in the tree :) Saying something like "recently merged" helps
here - otherwise I'll tend to read a message like that as saying that
the patch can't currently be applied due to other outstanding work.
next prev parent reply other threads:[~2010-11-05 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 18:35 [PATCH 0/3] sound card dir under debugfs Jarkko Nikula
2010-11-05 18:35 ` [PATCH 1/3] ASoC: Add sound card directory under debugfs/asoc/ Jarkko Nikula
2010-11-05 18:35 ` [PATCH 2/3] ASoC: Move codec debugfs directories under parent card directory Jarkko Nikula
2010-11-05 18:35 ` [PATCH 3/3] ASoC: Move pop time from DAPM context to sound card Jarkko Nikula
2010-11-05 18:36 ` [PATCH 0/3] sound card dir under debugfs Mark Brown
2010-11-05 18:39 ` Jarkko Nikula
2010-11-05 18:39 ` Mark Brown
2010-11-05 18:41 ` Jarkko Nikula
2010-11-05 18:46 ` Mark Brown [this message]
2010-11-05 18:48 ` Jarkko Nikula
2010-11-05 18:50 ` Mark Brown
2010-11-06 10:52 ` Liam Girdwood
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=20101105184603.GC9139@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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).