From: Kohei Enju <enjuk@amazon.com>
To: <takamitz@amazon.co.jp>
Cc: <andrew@lunn.ch>, <anthony.l.nguyen@intel.com>,
<davem@davemloft.net>, <edumazet@google.com>,
<intel-wired-lan@lists.osuosl.org>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<przemyslaw.kitszel@intel.com>, Kohei Enju <enjuk@amazon.com>
Subject: Re: [PATCH v1 net-next] e1000e: Remove duplicated writel() in e1000_configure_tx/rx()
Date: Wed, 4 Sep 2024 15:41:01 +0900 [thread overview]
Message-ID: <20240904064101.8548-1-enjuk@amazon.com> (raw)
In-Reply-To: <20240904055646.58588-1-takamitz@amazon.co.jp>
> My colleague, Kohei, tested the patch with a real hardware and will provide his
> Tested-by shortly.
I have tested the patch using my physical hardware, an Intel Ethernet controller I219-V. The device was properly attached by the e1000e driver and functioned correctly. The test was performed on a custom kernel based on kernel-core-6.10.6-200.fc40.x86_64.
The PCI device is identified as an Intel Corporation Ethernet Connection (17) I219-V (rev 11), with vendor ID 0x8086 and device ID 0x1a1d. This device ID matches the E1000_DEV_ID_PCH_ADP_I219_V17 definition in the e1000e driver code.
```
$ lspci | grep -i ethernet
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (17) I219-V (rev 11)
$ cat /sys/bus/pci/devices/0000:00:1f.6/{vendor,device}
0x8086
0x1a1d
$ grep -ri 0x1a1d ~/ghq/github.com/torvalds/linux/drivers/net/ethernet/intel/e1000e
/home/kohei/ghq/github.com/torvalds/linux/drivers/net/ethernet/intel/e1000e/hw.h:#define E1000_DEV_ID_PCH_ADP_I219_V17 0x1A1D
```
So this testing confirms that the patch does not introduce any regressions for this specific hardware configuration.
Tested-by: Kohei Enju <enjuk@amazon.com>
Thanks!
next prev parent reply other threads:[~2024-09-04 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 6:14 [PATCH v1 net-next] e1000e: Remove duplicated writel() in e1000_configure_tx/rx() Takamitsu Iwai
2024-09-02 16:04 ` Andrew Lunn
2024-09-03 10:46 ` Takamitsu Iwai
2024-09-03 16:49 ` Andrew Lunn
2024-09-04 5:56 ` Takamitsu Iwai
2024-09-04 6:41 ` Kohei Enju [this message]
2024-09-04 12:13 ` Andrew Lunn
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=20240904064101.8548-1-enjuk@amazon.com \
--to=enjuk@amazon.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=takamitz@amazon.co.jp \
/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).