[PATCH net v3 04/11] list: Move on_list_rcu() to list.h and add on_list() also
Jakub Kicinski
kuba at kernel.org
Sun Mar 29 12:14:55 PDT 2026
On Thu, 26 Mar 2026 13:18:29 +0000 David Howells wrote:
> Unfortunately, list_empty() is not usable with an entry that has been
> removed from a list with list_del_rcu() as ->next must be left pointing at
> the following entry so as not to break traversal under RCU.
This seems to break build for jffs.
Someone already marked this as rejected in PW.
Whoever it was PLEASE STOP.
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
More information about the linux-afs
mailing list