Hi, Andrew,
On Mon, Jan 27, 2025 at 9:21 PM Andrew Lunn <andrew@xxxxxxx> wrote:
According to the rules a "bug" should break build or break runtime or
I'm not very familiar with the difference between net and net-next,
but I think this series should be backported to stable branches.
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
a security issue, but shouldn't be spelling fixes.
But from my point of view, this series is not just "spelling fixes",
and not "trivial fixes without benefit for users". It is obviously a
copy-paste error and may confuse developers, so I think the patches
really have "benefits".
No bug report is because MTL_MAX_RX_QUEUES is accidentally equal to
It must either fix a real bug that bothers people or just add a
device ID.
Does this really bother people? Have we seen bug reports?
MTL_MAX_TX_QUEUES and it just works, not because the logic is correct.
And Kunihiko's patch can also be treated as a report.
Goto net or goto net-next are both fine to me, I just think this
There is another aspect to this. We are adding warnings saying that
the device tree blob is broken. That should encourage users to upgrade
their device tree blob. But most won't find any newer version. If this
goes into net-next, the roll out will be a lot slower, developers on
the leading edge will find the DT issue and submit a DT patch. By the
time this is in a distro kernel, maybe most of the DT issues will
already be fixed?
series should be backported to stable branches. There are lots of
patches backported even though they are less important than this
series (maybe not in the network subsystem).