list: introduce list_next/prev_entry
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | list: introduce list_next_entry() and list_prev_entry()drivers/ include/ kernel/ | +16 | 0 replies | |
| 2/4 | list: change list_for_each_entry*() to use list_*_entry()include/ | +22 | 0 replies | |
| 3/4 | list: introduce list_last_entry(), use list_{first,last}_entry()include/ | +15 | 0 replies | |
| 4/4 | debugfs: use list_next_entry() in debugfs_remove_recursive()fs/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] list: introduce list_next/prev_entry
Hello.
Not sure who maintains list.h, hopefully this is -mm material.
It is really annoying that we do not have list_next/prev_entry, they can have a lot of users, including list.h itself.
And in fact list_next_entry() is already defined in events/core.c and bnx2x_sp.c, this proves that it is really handy. That is why 1/4 comes as a separate patch because it touches the code outside of list.h.
3/4 is minor, but I think makes sense anyway.
4/4 is just the random example of usage outside of list.h, list_entry(child->d_u.d_child.next, struct dentry, d_u.d_child) is hardly readable.
None of this patches changes the compiled code.
Oleg.
drivers/net/ethernet/broadcom/bnx2x/bnx2x_sp.c | 3 - fs/debugfs/inode.c | 3 +- include/linux/list.h | 79 ++++++++++++++++-------- kernel/events/core.c | 3 - 4 files changed, 54 insertions(+), 34 deletions(-)