From: Mark Brown <broonie@kernel.org>
To: Richard Leitner <dev@g0hl1n.net>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
eric@nelint.com, clemens.gruber@pqgruber.com, tiwai@suse.com,
perex@perex.cz, lgirdwood@gmail.com
Subject: Re: [PATCH v2] ASoC: sgtl5000: add headphone and LINEOUT mute controls
Date: Fri, 9 Sep 2016 11:17:19 +0100 [thread overview]
Message-ID: <20160909101719.GD27946@sirena.org.uk> (raw)
In-Reply-To: <20160909094645.64b7744a@g0hl1n.net>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Fri, Sep 09, 2016 at 09:46:45AM +0200, Richard Leitner wrote:
> Hi,
> any comments, updates or ideas for improvement on that patch?
>
> regards,
> Richard
>
> On Wed, 31 Aug 2016 09:26:31 +0200
> Richard Leitner <dev@g0hl1n.net> wrote:
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.
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. If there have been
review comments then people may be waiting for those to be addressed.
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-09 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 20:25 [PATCH] " Richard Leitner
2016-08-31 7:26 ` [PATCH v2] " Richard Leitner
2016-09-09 7:46 ` Richard Leitner
2016-09-09 10:17 ` Mark Brown [this message]
2016-10-10 12:52 ` Richard Leitner
2016-10-10 14:24 ` Mark Brown
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=20160909101719.GD27946@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens.gruber@pqgruber.com \
--cc=dev@g0hl1n.net \
--cc=eric@nelint.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®