diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2026-06-09 13:42:22 +0300 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2026-06-09 13:42:22 +0300 |
| commit | 193b76eb109ed3ed77400c6d493b2f495ca64d9e (patch) | |
| tree | 3556494521f91c61a8a59959b10f4cc80da7e297 /include/linux/memory | |
| parent | 69a4e74e4cc46bdc65586f600b8552cc10a2811a (diff) | |
| parent | 0360976d7ed5c69484d873afa34a22db4d04996f (diff) | |
| download | linux-193b76eb109ed3ed77400c6d493b2f495ca64d9e.tar.xz | |
Merge branch 'netconsole-fix-reported-problems'
Breno Leitao says:
====================
netconsole: Fix reported problems
These are some of the issues that LLM reported to netconsole, and they
are being addressed here before big refactors.
I was doing some big refactors, and got some "pre-existent-issues"
during LLM review of the refactor, that make them hard to guarantee that
refactor is not introducing any bug, so, let's clean these pre-existent
bugs first, and then submit the refactor.
The issues fixed in this patchset were reported during the review of
https://lore.kernel.org/all/20260524-netconsole_move_more-v1-0-909d1ab398b4@debian.org/
Not all of them got fixed, but, those that were easy to reason about.
Why net-next and not 'net' tree.
Most of the functions that are being fixed here moved from netpoll to
netconsole, thus, fixing this on net will cause merge conflicts from
'net' to 'net-next', thus I decided to fix it on 'net-next', given we
are on 7.1-rc6 already. Sorry if that is not the right approach.
====================
Link: https://patch.msgid.link/20260604-netcons_fix_before_move-v3-0-ab055b3a6aa5@debian.org
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'include/linux/memory')
0 files changed, 0 insertions, 0 deletions