From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Ravi Kerur <rkerur@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] Add support for Intel chipsets
Date: Fri, 25 Sep 2015 08:04:01 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC0909020911F3@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20345734.BlVfqR1MBs@xps13>
Hi all,
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, September 25, 2015 3:08 PM
> To: Ravi Kerur
> Cc: dev@dpdk.org; Lu, Wenzhuo
> Subject: Re: [dpdk-dev] [PATCH v1] Add support for Intel chipsets
>
> 2015-09-24 15:13, Ravi Kerur:
> > M. Jay(Jayakumar, Muthurajan<muthurajan.jayakumar@intel.com>) and I
> > discussed and decided to include support for I217/I218 chipsets
> [...]
> > drivers/net/e1000/base/e1000_api.c | 1 +
> > drivers/net/e1000/base/e1000_hw.h | 1 +
> > drivers/net/e1000/base/e1000_ich8lan.c | 30 +++++++-----------------
> > drivers/net/e1000/base/e1000_osdep.h | 24 +++++++++++++++----
>
> You are modifying the base driver which is only allowed by Intel. But there can
> be exceptions. Wenzhuo, is it an exception?
I'm afraid it's not an exception. We plan to update e1000 base code recently. Hope it will help.
Thanks.
next prev parent reply other threads:[~2015-09-25 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 22:13 Ravi Kerur
2015-09-24 22:14 ` [dpdk-dev] [PATCH v1] Add support for I217 and I218 Intel 1G chipsets Ravi Kerur
2015-09-24 23:31 ` Jayakumar, Muthurajan
2015-09-25 7:08 ` [dpdk-dev] [PATCH v1] Add support for Intel chipsets Thomas Monjalon
2015-09-25 8:04 ` Lu, Wenzhuo [this message]
2015-09-25 21:13 ` Ravi Kerur
2015-09-28 1:11 ` Lu, Wenzhuo
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=6A0DE07E22DDAD4C9103DF62FEBC0909020911F3@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.com \
--cc=thomas.monjalon@6wind.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;
as well as URLs for NNTP newsgroup(s).