Re: [PATCH 0/3] Revert "revocable: Revocable resource management"

["Danilo Krummrich" <dakr@kernel.org>]

On Fri Jan 30, 2026 at 10:12 AM CET, Laurent Pinchart wrote:
> On Thu, Jan 29, 2026 at 03:01:50PM +0000, Tzung-Bi Shih wrote:
>> FWIW: https://lore.kernel.org/all/20260129143733.45618-2-tzungbi@kernel.org/
>> and https://lore.kernel.org/all/20260129143733.45618-4-tzungbi@kernel.org/
>> are the proposed fixes.
>
> I won't review that, sorry. As multiple people said in this mail thread,
> the API needs to go back to the design board.

Of course, you are entirely free to choose what you want to review, but I think
the justification you give is not entirely fair.

The patch series was on the list since August, you were explicitly Cc'd from the
get-go.

In v3 you said:

"To be clear, I'm not against the API being merged for the use cases that would
benefit from it, but I don't want to see drivers using it to protect from the
cdev/unregistration race."

This was a reply to Bartosz saying:

"Yeah, I'm not against this going upstream. If more development is needed for
this to be usable in other parts of the kernel, that can be done gradually.
Literally no subsystem ever was perfect on day 1."

Just to be clear, I'm not saying there are no issues to be addressed. And I'm
also not saying that you never raised concerns, you clearly did.

But, given the above, I don't think it's fair to request a revert as a
precondition to give constructive feedback for improvements and fixes.

- Danilo

Link: https://lore.kernel.org/chrome-platform/20250912145416.GL31682@pendragon.ideasonboard.com/