On Tue, Feb 18, 2025 at 04:15:43PM +0100, Ahmad Fatoum wrote: > On 18.02.25 16:05, Mark Brown wrote: > > On Mon, Feb 17, 2025 at 06:54:06PM -0800, Andrew Morton wrote: > >> The patch titled > >> Subject: regulator: allow user configuration of hardware protection action > >> has been added to the -mm mm-nonmm-unstable branch. Its filename is > >> regulator-allow-user-configuration-of-hardware-protection-action.patch > > This patch was posted less than 24 hours ago, after I last looked at my > > mail yesterday. There's not been *any* chance for review here, I'm > > still triaging my inbox today. > Did you receive v2 of my patch series[1] that was sent last month? > The only difference in this particular patch between v2 and v3 are > two Reviewed-by tags that were posted in the meantime. > I haven't sent out many patches crossing subsystems before, so please > let me know how to better handle this in future. > [1]: https://lore.kernel.org/all/20250113-hw_protection-reboot-v2-8-161d3fc734f0@xxxxxxxxxxxxxx/ That seems to have some noticable subthreads on it, such as Matti's one (if people don't cut any context from their mails it's hard to spot all the new content, even if that's tags...), and people were suggesting revisions there. It was also posted *just* before the merge window, far too late to go in so I'd be expecting a new version after the merge window. The problem here isn't you posting the patches, the problem is them getting applied with absolutely no time for review. Between v3 having been on the list for less than 24 hours and v2 coming out at the end of the previous release cycle there should've been *some* checking that subsystems are OK.
Attachment:
signature.asc
Description: PGP signature
