DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Zhang Haoyu" <zhanghy@sangfor.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [question] DPDK-2.0 support broadcom driver
Date: Wed, 3 Dec 2014 10:04:43 -0800	[thread overview]
Message-ID: <20141203100443.6518bb13@urahara> (raw)
In-Reply-To: <201412030948566609305@sangfor.com>

On Wed, 3 Dec 2014 09:48:57 +0800
"Zhang Haoyu" <zhanghy@sangfor.com> wrote:

> Hi,
> 
> I see that broadcom driver will be supported in DPDK-2.0 from 
> DPDK roadmap(http://dpdk.org/dev/roadmap),
> any details about the progress?
> 
> And, is there a plane for supporting emulex driver?
> 
> Thanks,
> Zhang Haoyu
> 

I have patch, just too big for mailing list.

  reply	other threads:[~2014-12-03 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  1:48 Zhang Haoyu
2014-12-03 18:04 ` Stephen Hemminger [this message]
2014-12-03 18:19   ` Thomas Monjalon
2014-12-04  2:58     ` Qiu, Michael

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=20141203100443.6518bb13@urahara \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=zhanghy@sangfor.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).