From: Simon Horman <horms@kernel.org>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: linma@zju.edu.cn, davem@davemloft.net,
gregkh@linuxfoundation.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v4] net: atm: Fix incorrect net_device lec check
Date: Tue, 8 Jul 2025 13:56:43 +0100 [thread overview]
Message-ID: <20250708125643.GH452973@horms.kernel.org> (raw)
In-Reply-To: <20250707175558.3137384-1-kuniyu@google.com>
On Mon, Jul 07, 2025 at 05:55:58PM +0000, Kuniyuki Iwashima wrote:
...
> Given all the recent commits are odd bug fixes and there are more bugs
> (e.g. firing netdev watchdog infinitely, lack of netns_immutable, etc),
> I'm leaning towards removing lec and mpc completely. I don't think it's
> still used nowadays.
Yes, I agree that we should consider removing such code entirely.
...
prev parent reply other threads:[~2025-07-08 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 5:28 [PATCH net v4] net: atm: Fix incorrect net_device lec check Lin Ma
2025-07-05 5:55 ` Greg KH
2025-07-07 17:55 ` Kuniyuki Iwashima
2025-07-08 12:56 ` Simon Horman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250708125643.GH452973@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).