linux-kernel - Re: [PATCH net-next 0/5] dpll: zl3073x: Add support for devlink flash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19fb41dc-4e24-49dc-a095-9e330acc42de@redhat.com>
Date: Fri, 25 Jul 2025 19:59:59 +0200
From: Ivan Vecera <ivecera@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, Jiri Pirko <jiri@...nulli.us>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
 Jonathan Corbet <corbet@....net>,
 Prathosh Satish <Prathosh.Satish@...rochip.com>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, Michal Schmidt <mschmidt@...hat.com>,
 Petr Oros <poros@...hat.com>
Subject: Re: [PATCH net-next 0/5] dpll: zl3073x: Add support for devlink flash

Hi Kuba,

On 25. 07. 25 7:42 odp., Jakub Kicinski wrote:
> On Fri, 25 Jul 2025 19:18:55 +0200 Ivan Vecera wrote:
>> Self nacked, need to fix warnings found by clang (not identified by
>> gcc).
> 
> Thanks for the note, I suppose you updated the patchwork state
> yourself? Please prefer using pw-bot commands in networking and bpf.

Will do next time, thanks for the note.

> (BTW net-next is closed already)

Oops, I missed this... will send v2 once the net-next will be open.

Thanks,
Ivan

> Quoting documentation:
> 
>    Updating patch status
>    ~~~~~~~~~~~~~~~~~~~~~
>    
>    Contributors and reviewers do not have the permissions to update patch
>    state directly in patchwork. Patchwork doesn't expose much information
>    about the history of the state of patches, therefore having multiple
>    people update the state leads to confusion.
>    
>    Instead of delegating patchwork permissions netdev uses a simple mail
>    bot which looks for special commands/lines within the emails sent to
>    the mailing list. For example to mark a series as Changes Requested
>    one needs to send the following line anywhere in the email thread::
>    
>      pw-bot: changes-requested
>    
>    As a result the bot will set the entire series to Changes Requested.
>    This may be useful when author discovers a bug in their own series
>    and wants to prevent it from getting applied.
>    
>    The use of the bot is entirely optional, if in doubt ignore its existence
>    completely. Maintainers will classify and update the state of the patches
>    themselves. No email should ever be sent to the list with the main purpose
>    of communicating with the bot, the bot commands should be seen as metadata.
>    
>    The use of the bot is restricted to authors of the patches (the ``From:``
>    header on patch submission and command must match!), maintainers of
>    the modified code according to the MAINTAINERS file (again, ``From:``
>    must match the MAINTAINERS entry) and a handful of senior reviewers.
>    
>    Bot records its activity here:
>    
>      https://netdev.bots.linux.dev/pw-bot.html
>    
> See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#updating-patch-status
>