From: Nicolin Chen <nicoleotsuka@gmail.com>
To: gabrielcsmo@gmail.com
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
linuxppc-dev@lists.ozlabs.org, Timur Tabi <timur@kernel.org>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>,
Yue Haibing <yuehaibing@huawei.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Mark Brown <broonie@kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH -next] ASoC: fsl_micfil: Remove set but not used variable 'osr'
Date: Wed, 17 Apr 2019 12:14:07 -0700 [thread overview]
Message-ID: <20190417191406.GA14405@Asurada-Nvidia.nvidia.com> (raw)
In-Reply-To: <3228ff50862b0bad95561bd5276cbfcad5d6213c.camel@gmail.com>
On Wed, Apr 17, 2019 at 09:58:37PM +0300, gabrielcsmo@gmail.com wrote:
> Nicolin, I am pretty sure I've ran the get_maintainer.pl script but
> I will pay more attention next time... sorry if I forgot to add you.
It's okay for that one as I trust Mark's review anyway. Just
adding us would offload some of his burden, especially for a
device specific change.
Thanks
next prev parent reply other threads:[~2019-04-17 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 15:09 [PATCH -next] ASoC: fsl_micfil: Remove set but not used variable 'osr' Yue Haibing
2019-04-17 15:25 ` Daniel Baluta
2019-04-17 18:35 ` Nicolin Chen
2019-04-17 18:58 ` gabrielcsmo
2019-04-17 19:14 ` Nicolin Chen [this message]
2019-04-17 16:42 ` Applied "ASoC: fsl_micfil: Remove set but not used variable 'osr'" to the asoc tree Mark Brown
2019-05-02 2:18 ` 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=20190417191406.GA14405@Asurada-Nvidia.nvidia.com \
--to=nicoleotsuka@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=festevam@gmail.com \
--cc=gabrielcsmo@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=perex@perex.cz \
--cc=timur@kernel.org \
--cc=tiwai@suse.com \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).