From: Kraus, NechamaX <nechamax.kraus@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v1 1/2] e1000e: Separate TGP board type from SPT
Date: Wed, 6 Oct 2021 15:23:48 +0300 [thread overview]
Message-ID: <1945444a-ed8a-d230-1334-3c2485ea2f94@linux.intel.com> (raw)
In-Reply-To: <20210922065449.3780338-1-sasha.neftin@intel.com>
On 9/22/2021 09:54, Sasha Neftin wrote:
> We have a same LAN controller on different PCH.
> Separate TGP board type from SPT will alllow apply specific fixes
> for TGP platforms.
>
> Suggested-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
> ---
> drivers/net/ethernet/intel/e1000e/e1000.h | 4 +-
> drivers/net/ethernet/intel/e1000e/ich8lan.c | 20 +++++++++
> drivers/net/ethernet/intel/e1000e/netdev.c | 45 +++++++++++----------
> 3 files changed, 46 insertions(+), 23 deletions(-)
>
Tested-by: Nechama Kraus <nechamax.kraus@linux.intel.com>
prev parent reply other threads:[~2021-10-06 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 6:54 [Intel-wired-lan] [PATCH v1 1/2] e1000e: Separate TGP board type from SPT Sasha Neftin
2021-09-22 7:03 ` Paul Menzel
[not found] ` <c6299a3e-61fc-8d6e-7023-10bc10e8483b@intel.com>
2021-09-22 13:56 ` Mark Pearson
2021-10-06 12:23 ` Kraus, NechamaX [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=1945444a-ed8a-d230-1334-3c2485ea2f94@linux.intel.com \
--to=nechamax.kraus@linux.intel.com \
--cc=intel-wired-lan@osuosl.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