mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Yun Zhou <yun.zhou@windriver.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	ying.xue@windriver.com, richard.danter@windriver.com
Subject: Re: [v2][PATCH] spi: use specific last_cs instead of last_cs_enable
Date: Fri, 25 Feb 2022 13:22:29 +0000	[thread overview]
Message-ID: <YhjYFc2HaGjydMqO@sirena.org.uk> (raw)
In-Reply-To: <4d621283-2a48-35ec-2131-1471a6b94c51@windriver.com>

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

On Fri, Feb 25, 2022 at 04:22:01PM +0800, Yun Zhou wrote:

> Do you have any comments on the new patch? It just fixes the
> regression introduced by d40f0b6f2e21, and it no longer affect cs_change.

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:[~2022-02-25 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 14:12 Yun Zhou
2022-02-25  8:22 ` Yun Zhou
2022-02-25 13:22   ` Mark Brown [this message]
2022-02-28 22:00 ` 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=YhjYFc2HaGjydMqO@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=richard.danter@windriver.com \
    --cc=ying.xue@windriver.com \
    --cc=yun.zhou@windriver.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®