All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: David Rhodes <david.rhodes@cirrus.com>
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org,
	ckeepax@opensource.cirrus.com, lgirdwood@gmail.com
Subject: Re: [alsa-devel] [PATCH v2] ASoC: wm_adsp: Expose mixer control API
Date: Mon, 18 Nov 2019 11:51:14 +0000	[thread overview]
Message-ID: <20191118115114.GA9761@sirena.org.uk> (raw)
In-Reply-To: <1573847653-17094-1-git-send-email-david.rhodes@cirrus.com>


[-- Attachment #1.1: Type: text/plain, Size: 509 bytes --]

On Fri, Nov 15, 2019 at 01:54:12PM -0600, David Rhodes wrote:
> 
> Changes since v1:
>   Updated commit message
>   Handle controls without subname
>   Call snd_ctl_notify() in wm_adsp_write_ctl()

Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff.  This reduces mail volume and ensures that 
any important information is recorded in the changelog rather than being
lost. 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      parent reply	other threads:[~2019-11-18 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 19:54 [alsa-devel] [PATCH v2] ASoC: wm_adsp: Expose mixer control API David Rhodes
2019-11-15 19:54 ` [alsa-devel] [PATCH] " David Rhodes
2019-11-18 13:46   ` Charles Keepax
2019-11-18 17:48   ` [alsa-devel] Applied "ASoC: wm_adsp: Expose mixer control API" to the asoc tree Mark Brown
2019-11-18 11:51 ` 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=20191118115114.GA9761@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.cirrus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.