Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: vishnu <vravulap@amd.com>
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
	MANAGEM..." <alsa-devel@alsa-project.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	open list <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.com>, YueHaibing <yuehaibing@huawei.com>,
	pierre-louis.bossart@linux.intel.com,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Alexander.Deucher@amd.com, djkurtz@google.com,
	Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
	Ravulapati Vishnu vardhan rao
	<Vishnuvardhanrao.Ravulapati@amd.com>,
	"Tabian, Reza" <Reza.Tabian@amd.com>
Subject: Re: [alsa-devel] [PATCH v14 7/7] ASoC: amd MMAP_INTERLEAVED Support
Date: Thu, 19 Dec 2019 13:15:54 +0000	[thread overview]
Message-ID: <20191219131554.GF5047@sirena.org.uk> (raw)
In-Reply-To: <3688990f-0ac3-08bf-20b8-93a4ab17441e@amd.com>


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

On Wed, Dec 18, 2019 at 11:59:56AM +0530, vishnu wrote:
> Hi Mark,
> 
> Patches have been reviewed by Dan and pierre-louis.bossart@linux.intel.com

I see no reviewed-by tags on most of this.

> Please can you upstream these please.

No, I will review them first.  Given the problems that have been seen on
previous reviews I don't intend to rush that.

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 adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

[-- 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

      reply	other threads:[~2019-12-19 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1575553053-18344-1-git-send-email-Vishnuvardhanrao.Ravulapati@amd.com>
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 1/7] ASoC: amd:Create multiple I2S platform device endpoint Ravulapati Vishnu vardhan rao
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 2/7] ASoC: amd: Refactoring of DAI from DMA driver Ravulapati Vishnu vardhan rao
2019-12-27  1:07   ` Mark Brown
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 3/7] ASoC: amd: Enabling I2S instance in DMA and DAI Ravulapati Vishnu vardhan rao
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 4/7] ASoC: amd: add ACP3x TDM mode support Ravulapati Vishnu vardhan rao
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 5/7] ASoC: amd: Handle ACP3x I2S-SP Interrupts Ravulapati Vishnu vardhan rao
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 6/7] ASoC: amd: Added ACP3x system resume and runtime pm Ravulapati Vishnu vardhan rao
2019-12-05 13:37 ` [alsa-devel] [PATCH v14 7/7] ASoC: amd MMAP_INTERLEAVED Support Ravulapati Vishnu vardhan rao
2019-12-18  6:29   ` vishnu
2019-12-19 13:15     ` 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=20191219131554.GF5047@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=Reza.Tabian@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=Vishnuvardhanrao.Ravulapati@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=djkurtz@google.com \
    --cc=gustavo@embeddedor.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=vravulap@amd.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