mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Agrawal, Akshu" <Akshu.Agrawal@amd.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
	Adam.Thomson.Opensource@diasemi.com, Alexander.Deucher@amd.com,
	Support.Opensource@diasemi.com, perex@perex.cz, tiwai@suse.com,
	Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ASoC: da7219: read fmw property to get mclk for non-dts systems
Date: Thu, 17 May 2018 15:13:21 +0900	[thread overview]
Message-ID: <20180517061321.GJ20254@sirena.org.uk> (raw)
In-Reply-To: <516fabd6-264d-a7bd-bf11-40d02154b1ef@amd.com>

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]

On Tue, May 15, 2018 at 03:13:47PM +0530, Agrawal, Akshu wrote:

> If you are Ok with this patch can you please take this.

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

  reply	other threads:[~2018-05-17 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  7:58 Akshu Agrawal
2018-05-04  9:15 ` Adam Thomson
2018-05-07  4:50   ` Agrawal, Akshu
2018-05-07  6:39     ` Daniel Kurtz
2018-05-15  9:43       ` Agrawal, Akshu
2018-05-17  6:13         ` Mark Brown [this message]
2018-05-16  9:37     ` Adam Thomson

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=20180517061321.GJ20254@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Adam.Thomson.Opensource@diasemi.com \
    --cc=Akshu.Agrawal@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Support.Opensource@diasemi.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=djkurtz@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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

all inboxes | Powered by JetHome®