All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vishal Thanki <vishalthanki@gmail.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Arvind Yadav <arvind.yadav.cs@gmail.com>,
	alsa-devel@alsa-project.org,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	elfring@users.sourceforge.net
Subject: Re: [PATCH 1/1] ASoC: davinci-mcasp: Only disable inactive serializer
Date: Tue, 27 Mar 2018 19:57:34 +0800	[thread overview]
Message-ID: <20180327115734.GE29239@sirena.org.uk> (raw)
In-Reply-To: <CAC3a_SDgNjxGLZu72zuecJV7e=0STWH8fUafK1h-7jFdGpM-vw@mail.gmail.com>


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

On Tue, Mar 27, 2018 at 01:34:55PM +0200, Vishal Thanki wrote:

> Just a gentle reminder, can this patch be accepted for the next release?

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 #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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



  reply	other threads:[~2018-03-27 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 14:51 [PATCH 0/1] Handling of serializers Vishal Thanki
2018-02-27 14:51 ` [PATCH 1/1] ASoC: davinci-mcasp: Only disable inactive serializer Vishal Thanki
2018-03-05 12:42   ` Peter Ujfalusi
2018-03-27 11:34     ` Vishal Thanki
2018-03-27 11:57       ` Mark Brown [this message]
2018-03-27 11:58       ` Mark Brown
2018-05-17 16:38   ` Applied "ASoC: davinci-mcasp: Only disable inactive serializer" to the asoc tree 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=20180327115734.GE29239@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=elfring@users.sourceforge.net \
    --cc=peter.ujfalusi@ti.com \
    --cc=vishalthanki@gmail.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.