From: Santhosh Kumar K <s-k6@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <miquel.raynal@bootlin.com>, <vigneshr@ti.com>, <marex@denx.de>,
<computersforpeace@gmail.com>, <theo.lebrun@bootlin.com>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<praneeth@ti.com>, <p-mantena@ti.com>, <a-dutta@ti.com>,
<u-kumar1@ti.com>, <s-k6@ti.com>
Subject: Re: [PATCH v2 0/4] Miscellaneous fixes and clean-ups
Date: Thu, 11 Sep 2025 17:03:55 +0530 [thread overview]
Message-ID: <bac6b719-8b40-4cdc-a72f-bd612c2d8510@ti.com> (raw)
In-Reply-To: <d52cb067-c89e-4f61-8305-031315585e55@sirena.org.uk>
Hello Mark,
On 11/09/25 16:46, Mark Brown wrote:
> On Thu, Sep 11, 2025 at 11:57:05AM +0530, Santhosh Kumar K wrote:
>
>> Gentle ping on 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 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.
I understand the concern, and apologies for the follow-up.
The first three patches already carry reviewed-by, and the fourth is
only a macro changes with no functional impact. Given that the merge
window is approaching, I thought it would be reasonable to send a gentle
reminder.
Regards,
Santhosh.
prev parent reply other threads:[~2025-09-11 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 18:59 [PATCH v2 0/4] Miscellaneous fixes and clean-ups Santhosh Kumar K
2025-09-05 18:59 ` [PATCH v2 1/4] spi: cadence-quadspi: Flush posted register writes before INDAC access Santhosh Kumar K
2025-09-05 18:59 ` [PATCH v2 2/4] spi: cadence-quadspi: Flush posted register writes before DAC access Santhosh Kumar K
2025-09-05 18:59 ` [PATCH v2 3/4] spi: cadence-quadspi: Fix cqspi_setup_flash() Santhosh Kumar K
2025-09-05 18:59 ` [PATCH v2 4/4] spi: cadence-quadspi: Use BIT() macros where possible Santhosh Kumar K
2025-09-11 6:27 ` [PATCH v2 0/4] Miscellaneous fixes and clean-ups Santhosh Kumar K
2025-09-11 11:16 ` Mark Brown
2025-09-11 11:33 ` Santhosh Kumar K [this message]
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=bac6b719-8b40-4cdc-a72f-bd612c2d8510@ti.com \
--to=s-k6@ti.com \
--cc=a-dutta@ti.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=p-mantena@ti.com \
--cc=praneeth@ti.com \
--cc=theo.lebrun@bootlin.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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