From: Dimitris Papavasiliou <dpapavas@gmail.com>
To: Mark Brown <broonie@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: alsa-devel@alsa-project.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
kernel-janitors@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: pcm512x: Fix a double unlock in pcm512x_digital_mute()
Date: Fri, 21 Dec 2018 13:54:26 +0000 [thread overview]
Message-ID: <87751c04-3bb9-0fc2-5ddc-2dd86dbe9b05@gmail.com> (raw)
In-Reply-To: <20181221121050.GE4996@sirena.org.uk>
On 12/21/18 2:10 PM, Mark Brown wrote:
> On Fri, Dec 21, 2018 at 03:00:56PM +0300, Dan Carpenter wrote:
>> On Fri, Dec 21, 2018 at 01:23:37PM +0200, Dimitris Papavasiliou wrote:
>
>>> Maintainers, please let me know if there's anything I need to do
>>> with respect to this.
>
>> All you need to is reply with a reviewed-by tag so we can mark on the
>> fix that you approved it.
>
>> Reviewed-by: Your Name <email>
>
> I've just gone and applied the tag but yeah, what Dan says - there's
> tools that can pick tags like this out of e-mail which is also useful.
Thanks to both, but Mark, I'm afraid you've misspelled "Reviewed" in
the patch you applied.
next prev parent reply other threads:[~2018-12-21 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 9:11 [PATCH] ASoC: pcm512x: Fix a double unlock in pcm512x_digital_mute() Dan Carpenter
2018-12-21 11:23 ` Dimitris Papavasiliou
2018-12-21 12:00 ` Dan Carpenter
2018-12-21 12:10 ` Mark Brown
2018-12-21 13:54 ` Dimitris Papavasiliou [this message]
2018-12-21 13:42 ` Applied "ASoC: pcm512x: Fix a double unlock in pcm512x_digital_mute()" to the asoc tree Mark Brown
2018-12-21 13:51 ` [PATCH] ASoC: pcm512x: Fix a double unlock in pcm512x_digital_mute() Dimitris Papavasiliou
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=87751c04-3bb9-0fc2-5ddc-2dd86dbe9b05@gmail.com \
--to=dpapavas@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--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