From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Andrew Lunn <andrew@lunn.ch>,
"Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>
Cc: Seongjun Hong <hsj0512@snu.ac.kr>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH] e1000: drop dead switch statements in configure_tx/rx
Date: Thu, 30 Jul 2026 14:08:28 -0700 [thread overview]
Message-ID: <7d4b3b11-e303-4e02-aed9-802e76381836@intel.com> (raw)
In-Reply-To: <a422c52e-27de-4c10-93ca-4e82e7cbc517@lunn.ch>
On 7/29/2026 8:00 AM, Andrew Lunn wrote:
>> I see the point, but as the code is quite old and its extensive development
>> period passed long time ago, i believe value of such cosmetic patches is
>> rather questionable.
>
> It might be worth looking at the history of this code and see why it
> is this way. Sometimes odd code like this is actually a bug of some
> sort, maybe a merge conflict resolution which want wrong.
Looks like this was introduced with 24025e4ecf88 ("e1000: implementation
of the multi-queue feature") and the multiqueue portion was removed with
c1605eb37aa6 ("e1000: Remove Multiqueue code until we have support for
MSI-X in our hardware"). I think it was intentional but probably an
oversight that this only left one path after the multiqueue removal.
Thanks,
Tony
prev parent reply other threads:[~2026-07-30 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 8:01 [Intel-wired-lan] [PATCH] e1000: drop dead switch statements in configure_tx/rx Seongjun Hong
2026-07-29 10:07 ` Jagielski, Jedrzej
2026-07-29 14:51 ` 홍성준
2026-07-29 15:00 ` Andrew Lunn
2026-07-30 21:08 ` Tony Nguyen [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=7d4b3b11-e303-4e02-aed9-802e76381836@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hsj0512@snu.ac.kr \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/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