Reviews by edumazet@google.com · linux-can

All review-attestation trailers (Reviewed-by / Acked-by / Tested-by / Reported-by / Suggested-by / Co-developed-by / Reported-and-tested-by) by this address on the linux-can archive.

31 attestations . (3 Reported-by, 20 Reviewed-by, 8 Suggested-by)

• STALE579d REVIEWED: 5 (5M) [PATCH net-next v7 1/4] sock: Introduce sk_set_prio_allowed helper function
  2024-12-13 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 7/9] net: inet6: do not leave a dangling sk pointer in inet6_create()
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 9/9] Revert "net: do not leave a dangling sk pointer, when socket creation fails"
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 8/9] net: warn, if pf->create does not clear sock->sk on error
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 6/9] net: inet: do not leave a dangling sk pointer in inet_create()
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 5/9] net: ieee802154: do not leave a dangling sk pointer in ieee802154_create()
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 3/9] Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 2/9] Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
  2024-10-15 · Reviewed-by
• STALE642d REVIEWED: 4 (4M) Re: [PATCH net-next v3 1/9] af_packet: avoid erroring out after sock_init_data() in packet_create()
  2024-10-15 · Reviewed-by
• STALE642d [PATCH net-next v3 1/9] af_packet: avoid erroring out after sock_init_data() in packet_create()
  2024-10-14 · Suggested-by
• STALE650d [PATCH v2 2/8] af_packet: avoid erroring out after sock_init_data() in packet_create()
  2024-10-07 · Suggested-by
• STALE1013d LANDED [net-next v3 4/5] net: tc35815: rework network interface interrupt logic
  2023-10-09 · Suggested-by
• STALE1013d LANDED: 4 (4M) [net-next v3 3/5] netdev: replace napi_reschedule with napi_schedule
  2023-10-09 · Reviewed-by
• STALE1013d LANDED: 4 (4M) [net-next v3 2/5] netdev: make napi_schedule return bool on NAPI successful schedule
  2023-10-09 · Suggested-by
• STALE1013d LANDED: 4 (4M) [net-next v3 2/5] netdev: make napi_schedule return bool on NAPI successful schedule
  2023-10-09 · Reviewed-by
• STALE1013d LANDED: 4 (4M) [net-next v3 1/5] netdev: replace simple napi_schedule_prep/__napi_schedule to napi_schedule
  2023-10-09 · Reviewed-by
• STALE1015d REVIEWED: 4 (4M) Re: [net-next PATCH v2 1/4] netdev: replace simple napi_schedule_prep/__napi_schedule to napi_schedule
  2023-10-05 · Reviewed-by
• STALE1015d REVIEWED: 4 (4M) Re: [net-next PATCH v2 3/4] netdev: replace napi_reschedule with napi_schedule
  2023-10-05 · Reviewed-by
• STALE1015d REVIEWED: 4 (4M) [net-next PATCH v2 2/4] netdev: make napi_schedule return bool on NAPI successful schedule
  2023-10-03 · Suggested-by
• STALE1015d REVIEWED: 4 (4M) [net-next PATCH v2 2/4] netdev: make napi_schedule return bool on NAPI successful schedule
  2023-10-03 · Reviewed-by
• STALE1021d REVIEWED: 4 (4M) Re: [net-next PATCH 2/4] netdev: make napi_schedule return bool on NAPI successful schedule
  2023-10-03 · Reviewed-by
• STALE1063d LANDED [NET 2/2] can: raw: add missing refcount for memory leak fix
  2023-08-21 · Reported-by
• STALE1063d REVIEWED: 4 (4M) Re: [PATCH net] net: validate veth and vxcan peer ifindexes
  2023-08-19 · Reviewed-by
• DORMANTno replies [PATCH] can: raw: add missing refcount for memory leak fix
  2023-08-15 · Reported-by
• STALE1070d [RFC PATCH] can: raw: add missing refcount for memory leak fix
  2023-08-04 · Reported-by
• STALE1542d REVIEWED: 4 (4M) Re: [PATCH net-next v3] net: SO_RCVMARK socket option for SO_MARK with recvmsg()
  2022-04-27 · Reviewed-by
• STALE1950d REVIEWED: 1 (1M) [net 5/6] can: skb: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership
  2021-03-01 · Suggested-by
• STALE1966d LANDED [PATCH net v4 1/1] can: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership
  2021-02-26 · Suggested-by
• STALE1972d REVIEWED: 4 (4M) Re: [PATCH net v3 1/1] can: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership
  2021-02-24 · Reviewed-by
• STALE1972d [PATCH net v3 1/1] can: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership
  2021-02-24 · Suggested-by
• STALE4554d REVIEWED: 4 (4M) Re: [PATCH stable 3.9+] can: add destructor for self generated skbs
  2014-01-30 · Reviewed-by