diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-03-11 19:04:58 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-03-11 19:04:58 -0700 |
| commit | e62a22f43475624ea466fd9b766f62e8458f4cd9 (patch) | |
| tree | 6e111b4fad09f0afa1691679259dd77df0e32fef /tools/perf/scripts/python/bin | |
| parent | e8f0dc024ce55451ebd54bad975134ba802e4fcc (diff) | |
| parent | 68e76fc12df091b04ede5f6244385a35abae0a80 (diff) | |
| download | linux-e62a22f43475624ea466fd9b766f62e8458f4cd9.tar.gz linux-e62a22f43475624ea466fd9b766f62e8458f4cd9.zip | |
Merge branch 'neighbour-fix-update-of-proxy-neighbour'
Sabrina Dubroca says:
====================
neighbour: fix update of proxy neighbour
While re-reading some "old" patches I ran into a small change of
behavior in commit dc2a27e524ac ("neighbour: Update pneigh_entry in
pneigh_create().").
The old behavior was not consistent between ->protocol and ->flags,
and didn't offer a way to clear protocol, so maybe it's better to
change that (7-years-old [1]) behavior. But then we should change
non-proxy neighbours as well to keep neigh/pneigh consistent.
[1] df9b0e30d44c ("neighbor: Add protocol attribute")
====================
Link: https://patch.msgid.link/cover.1772894876.git.sd@queasysnail.net
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions