From: Mark Brown <broonie@kernel.org>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Misbah Ullah Khan <Misbahk@danlawinc.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v4 3/4] ASoC: dapm: support mixer controls with mute at non-zero value
Date: Wed, 29 Jun 2016 19:09:03 +0100 [thread overview]
Message-ID: <20160629180903.GG6247@sirena.org.uk> (raw)
In-Reply-To: <7780cb9b-9d46-7cbb-501e-10a154ccc527@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Tue, Jun 28, 2016 at 10:12:37AM +0200, Peter Rosin wrote:
> Hi!
>
> Sorry to send a ping like this, with the patch still in patchwork
> and all. But it's been a month since 1/4 and 2/4 were committed
> and I expected at least some comment on the approach for patches
> 3 and 4...
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on holiday, attend conferences and so
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review. Sending content
free pings just adds to the mail volume (if they are seen at all) and if
something has gone wrong you'll have to resend the patches anyway.
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-29 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 21:09 [PATCH v4 0/4] ASoC: MAX9860: new driver Peter Rosin
2016-05-14 21:09 ` [PATCH v4 1/4] dt-bindings: sound: add bindings for the max9860 codec Peter Rosin
2016-05-27 20:24 ` Mark Brown
2016-05-27 20:40 ` Peter Rosin
2016-05-27 20:45 ` Mark Brown
2016-05-27 21:07 ` Peter Rosin
2016-05-14 21:09 ` [PATCH v4 2/4] ASoC: MAX9860: new driver Peter Rosin
2016-05-14 21:09 ` [PATCH v4 3/4] ASoC: dapm: support mixer controls with mute at non-zero value Peter Rosin
2016-06-28 8:12 ` Peter Rosin
2016-06-29 18:09 ` Mark Brown [this message]
2016-05-14 21:09 ` [PATCH v4 4/4] ASoC: MAX9860: add sidetone mixer control Peter Rosin
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=20160629180903.GG6247@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Misbahk@danlawinc.com \
--cc=alsa-devel@alsa-project.org \
--cc=galak@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=peda@axentia.se \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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