[PATCH net v3 RESEND 0/6] net: bcmasp: Collection of fixes

Florian Fainelli posted 6 patches 1 week, 3 days ago
drivers/net/ethernet/broadcom/asp2/bcmasp.c   | 121 ++++++++++--------
drivers/net/ethernet/broadcom/asp2/bcmasp.h   |   4 -
.../net/ethernet/broadcom/asp2/bcmasp_intf.c  |  32 ++++-
3 files changed, 95 insertions(+), 62 deletions(-)
[PATCH net v3 RESEND 0/6] net: bcmasp: Collection of fixes
Posted by Florian Fainelli 1 week, 3 days ago
This patch series is a collection of bug fixes accumulated during a LLM
coding session. Thanks to Justin for the internal review and helping
with the last patch.

Changes in v3:

- add Nicolai's and Justin's R-b tags where collected, except patch 6
  that did not make it to the mailing list somehow
- removed inline keyword from bcmasp_netfilt_is_companion per Nicolai's
  review

Changes in v2:

- address Sashiko's feedback and correct the commit messages and code
  accordingly
- add Nicolai's R-b tag where collected

Florian Fainelli (6):
  net: bcmasp: fix mib counters struct alignment with ethtool stats
  net: bcmasp: unmap previous DMA mappings on TX map failure
  net: bcmasp: validate minimum RX packet size in bcmasp_rx_poll()
  net: bcmasp: fix OF node reference leak for phy_dn
  net: bcmasp: account for offload header in TX short packet padding
  net: bcmasp: fix network filter lookup and wake filter pair allocation

 drivers/net/ethernet/broadcom/asp2/bcmasp.c   | 121 ++++++++++--------
 drivers/net/ethernet/broadcom/asp2/bcmasp.h   |   4 -
 .../net/ethernet/broadcom/asp2/bcmasp_intf.c  |  32 ++++-
 3 files changed, 95 insertions(+), 62 deletions(-)

-- 
2.34.1
Re: [PATCH net v3 RESEND 0/6] net: bcmasp: Collection of fixes
Posted by netdev-bot+sinfo@kernel.org 1 week, 3 days ago
Hi!

This is an automated message. This series looks like a fix, but its
commit messages seem to be missing some information:

 - Whether the issue was actually triggered, or is only theoretical
   (e.g. found by code inspection). If it was triggered please include
   the symptoms, like the stack trace or error messages.

 - What hardware the change was tested on. For driver fixes please
   mention the device (and if relevant firmware version) used for
   testing, or say that the change was not tested on real hardware.

Please do not repost the series just to address the above. Instead,
reply to this email with the missing information, so that reviewers
can take it into account. If the series needs another revision for
other reasons, please include the information in the commit messages
then.

The evaluation is done by an LLM so it may be wrong, if you think
that is the case please reply and explain.