public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Rajendra Nayak <rnayak@codeaurora.org>
Cc: viresh.kumar@linaro.org, sboyd@kernel.org,
	bjorn.andersson@linaro.org, agross@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	mka@chromium.org, Alok Chauhan <alokc@codeaurora.org>,
	Akash Asthana <akashast@codeaurora.org>,
	linux-spi@vger.kernel.org
Subject: Re: [PATCH v4 2/6] spi: spi-geni-qcom: Use OPP API to set clk/perf state
Date: Fri, 8 May 2020 12:57:41 +0100	[thread overview]
Message-ID: <20200508115741.GG4820@sirena.org.uk> (raw)
In-Reply-To: <acc7baf9-86a3-6c78-4d62-99d4b1baa12e@codeaurora.org>

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

On Thu, May 07, 2020 at 10:30:43PM +0530, Rajendra Nayak wrote:

> Mark, would you be able to review/ack this patch so it can be
> taken in via the msm tree? 'PATCH 1/6' is Ack'd by Greg, and its
> going to land via the msm tree as well.

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

  reply	other threads:[~2020-05-08 11:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 12:04 [PATCH v4 0/6] DVFS for IO devices on sdm845 and sc7180 Rajendra Nayak
2020-05-03 12:04 ` [PATCH v4 1/6] tty: serial: qcom_geni_serial: Use OPP API to set clk/perf state Rajendra Nayak
2020-05-03 12:04 ` [PATCH v4 2/6] spi: spi-geni-qcom: " Rajendra Nayak
2020-05-07 17:00   ` Rajendra Nayak
2020-05-08 11:57     ` Mark Brown [this message]
2020-05-03 12:04 ` [PATCH v4 3/6] drm/msm/dpu: " Rajendra Nayak
2020-05-03 12:04 ` [PATCH v4 4/6] drm/msm: dsi: " Rajendra Nayak
2020-05-03 12:04 ` [PATCH v4 5/6] media: venus: core: Add support for opp tables/perf voting Rajendra Nayak
2020-05-05 23:07   ` Matthias Kaehlcke
2020-05-06 10:26     ` Rajendra Nayak
2020-05-03 12:04 ` [PATCH v4 6/6] spi: spi-qcom-qspi: Use OPP API to set clk/perf state Rajendra Nayak
2020-05-05 16:38   ` Matthias Kaehlcke
2020-05-06 10:19     ` Rajendra Nayak

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=20200508115741.GG4820@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=agross@kernel.org \
    --cc=akashast@codeaurora.org \
    --cc=alokc@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=rnayak@codeaurora.org \
    --cc=sboyd@kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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