From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: disable bnx2x driver
Date: Tue, 28 Jul 2015 23:17:27 +0200 [thread overview]
Message-ID: <22831881.TPP2R9bdJg@xps13> (raw)
In-Reply-To: <1438103799-31340-1-git-send-email-thomas.monjalon@6wind.com>
2015-07-28 19:16, Thomas Monjalon:
> This driver has too many issues:
> - too big
> - bad coding style
> - no git history (dropped in 2 patches)
> - no documentation
> - no BSD support
> - no maintainer
> And the biggest one, constraining this disabling:
> - many build issues
>
> If the last 4 issues are not fixed in the next release 2.2,
> the driver must be removed.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied
next prev parent reply other threads:[~2015-07-28 21:18 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
2015-07-28 21:17 ` Thomas Monjalon [this message]
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=22831881.TPP2R9bdJg@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).