DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Ravi Kerur <rkerur@gmail.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Q on Support for I217 and I218 Intel chipsets.
Date: Thu, 15 Jan 2015 21:22:18 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C9972F@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CAFb4SLDs3wVDpOOLtH3Lg1h3+c8ZpzgKZUz3MMO17Akqoc1B9Q@mail.gmail.com>

> On Thursday, January 15, 2015  at 8:34 PM, Ravi Kerur <rkerur@gmail.com> wrote:
> 
> On Wed, Jan 14, 2015 at 8:27 AM, Thomas Monjalon
> <thomas.monjalon@6wind.com>
> wrote:
> 
> > 2015-01-09 04:41, Ravi Kerur:
> > > Thomas,
> > >
> > > Please let me know how I can move forward on this. If i confine changes
> > in
> > > e1000/ directory to e1000_osdep.h file only and the rest in PMD will that
> > > work? The reason I ask is because of following comment  in README file.
> > >
> > > ...
> > > Few changes to the original FreeBSD sources were made to:
> > > - Adopt it for PMD usage mode:
> > >         e1000_osdep.c
> > >         e1000_osdep.h
> > > ...
> >
> > This is an Intel driver so you should ask to the responsible of this code
> > at Intel.
> > The problem is that there is not really an identified responsible for this
> > driver.
> >
> > The rule is to not change the base driver, even osdep files.
> > But it would be better to have an exception here.
> >
> >
> > PS: please avoid top-posting.
> >
> 
> <rk> Please let me know who is the contact person from Intel so I can add
> him/her to "To" list when I send the patch or Should I contact Jim St Leger
> and ask him about this?

We're looking into this, but don't have a definitive answer yet. Somebody from Intel will reply as soon as we've confirmed whether the change you proposed is OK or not.


Tim

  reply	other threads:[~2015-01-15 21:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 23:28 Ravi Kerur
2015-01-05  8:55 ` Thomas Monjalon
2015-01-05 16:40   ` Ravi Kerur
2015-01-09 12:41     ` Ravi Kerur
2015-01-14 16:27       ` Thomas Monjalon
2015-01-15 20:34         ` Ravi Kerur
2015-01-15 21:22           ` O'driscoll, Tim [this message]
2015-01-15 23:54           ` Ananyev, Konstantin
2015-01-16 10:52             ` Bruce Richardson
2015-01-16 11:08               ` Ananyev, Konstantin
2015-01-16 11:31                 ` Bruce Richardson
2015-01-16 12:01                   ` Ananyev, Konstantin
2015-01-22  0:03                     ` Ravi Kerur
2015-01-16  1:14 ` Zhang, Helin
2015-01-16  1:43   ` Ravi Kerur

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=26FA93C7ED1EAA44AB77D62FBE1D27BA54C9972F@IRSMSX102.ger.corp.intel.com \
    --to=tim.o'driscoll@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).