[moderation/CI] Re: net: bridge: take care of p->flags accesses

syzbot ci has tested the following series

[v1] net: bridge: take care of p->flags accesses
https://lore.kernel.org/all/[email protected]
* [PATCH net-next 1/5] bridge: use atomic ops to read/change p->flags in sysfs
* [PATCH net-next 2/5] bridge: use atomic ops to read/change p->flags in br_netlink.c
* [PATCH net-next 3/5] net: bridge: use atomic ops to read/change p->flags (I)
* [PATCH net-next 4/5] net: bridge: use atomic ops to read/change p->flags (II)
* [PATCH net-next 5/5] net: bridge: use atomic ops to read/change p->flags (III)

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/af3c270e-aed1-483d-aca2-8e328e1d9aa9

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      67ad35a58a88c360136d893cbc4c7f5b14100bb9
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/866adee7-16cc-49c4-bfec-0fb43ebb02b2/config

net/bridge/br_mrp.c:1249:23: error: use of undeclared identifier 'BR_MRP_AWARE_BI'; did you mean 'BR_MRP_AWARE_BIT'?

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: [email protected]

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at [email protected].

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid