DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: disable bnx2x driver
Date: Tue, 28 Jul 2015 11:29:42 -0700	[thread overview]
Message-ID: <20150728112942.77309366@urahara> (raw)
In-Reply-To: <1438103799-31340-1-git-send-email-thomas.monjalon@6wind.com>

On Tue, 28 Jul 2015 19:16:39 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:

> This driver has too many issues:
> 	- too big
> 	- bad coding style
> 	- no git history (dropped in 2 patches)
> 	- no documentation
> 	- no BSD support

The main issue with BSD is loading the firmware.
Probably just need to change the path.

  reply	other threads:[~2015-07-28 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 17:16 Thomas Monjalon
2015-07-28 18:29 ` Stephen Hemminger [this message]
2015-07-28 21:17 ` Thomas Monjalon
2015-07-28 21:38 ` Stephen Hemminger

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