All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shreyas Joshi <Shreyas.Joshi@biamp.com>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"shreyasjoshi15@gmail.com" <shreyasjoshi15@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: spi-cadence: add support for chip select high
Date: Mon, 20 Jul 2020 13:54:50 +0100	[thread overview]
Message-ID: <20200720125450.GE4601@sirena.org.uk> (raw)
In-Reply-To: <MN2PR17MB29743B1AE9419961F152EC73FC7B0@MN2PR17MB2974.namprd17.prod.outlook.com>

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

On Mon, Jul 20, 2020 at 03:55:55AM +0000, Shreyas Joshi wrote:
> Were you able to patch my driver successfully?
> 
> -----Original Message-----

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-07-20 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  4:51 [PATCH] spi: spi-cadence: add support for chip select high Shreyas Joshi
2020-07-10 15:35 ` Mark Brown
2020-07-10 21:16 ` Shreyas Joshi
2020-07-20  3:55   ` Shreyas Joshi
2020-07-20 12:54     ` Mark Brown [this message]
2020-07-21  0:08   ` Shreyas Joshi
2020-07-22 13:45   ` 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=20200720125450.GE4601@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Shreyas.Joshi@biamp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=shreyasjoshi15@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.