Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches

[Florian Fainelli <f.fainelli@gmail.com>]

On 3/27/23 10:26, Jakub Kicinski wrote:
> We don't state explicitly that reverts need to be submitted
> as a patch. It occasionally comes up.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: corbet@lwn.net
> CC: linux-doc@vger.kernel.org
> ---
>   Documentation/process/maintainer-netdev.rst | 9 ++++++++-
>   1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst
> index e31d7a951073..f6983563ff06 100644
> --- a/Documentation/process/maintainer-netdev.rst
> +++ b/Documentation/process/maintainer-netdev.rst
> @@ -184,11 +184,18 @@ Handling misapplied patches
>   
>   Occasionally a patch series gets applied before receiving critical feedback,
>   or the wrong version of a series gets applied.
> -There is no revert possible, once it is pushed out, it stays like that.
> +
> +Making the patch disappear once it is pushed out is not possible, the commit
> +history in netdev trees is stable.

I would write immutable instead of stable here to convey the idea that 
there are no history rewrites once the tree is pushed out. With that:

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
-- 
Florian