[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bac6b719-8b40-4cdc-a72f-bd612c2d8510@ti.com>
Date: Thu, 11 Sep 2025 17:03:55 +0530
From: Santhosh Kumar K <s-k6@...com>
To: Mark Brown <broonie@...nel.org>
CC: <miquel.raynal@...tlin.com>, <vigneshr@...com>, <marex@...x.de>,
<computersforpeace@...il.com>, <theo.lebrun@...tlin.com>,
<linux-spi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<praneeth@...com>, <p-mantena@...com>, <a-dutta@...com>,
<u-kumar1@...com>, <s-k6@...com>
Subject: Re: [PATCH v2 0/4] Miscellaneous fixes and clean-ups
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.
Powered by blists - more mailing lists