From: Yotam Rubin <yotam@weka.io>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 4/4] bnx2x: enable PMD build
Date: Wed, 17 Jun 2015 14:19:27 +0300 [thread overview]
Message-ID: <CABD4VVAOWEoN3P=ZNarGjdAwBYAaUjFz88=9kzMfkMm0DjGm+g@mail.gmail.com> (raw)
In-Reply-To: <1434498700-8522-5-git-send-email-stephen@networkplumber.org>
On Wed, Jun 17, 2015 at 2:51 AM, Stephen Hemminger <
stephen@networkplumber.org> wrote:
[...]
>
> +/****************** Qualcom devices ******************/
> +
> +/* Broadcom/Qualcom BNX2X */
>
>
I suppose you meant QLogic, rather than Qualcomm?
>
> --
> 2.1.4
>
>
next prev parent reply other threads:[~2015-06-17 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 23:51 [dpdk-dev] [PATCH 0/4 v5] bnx2x: poll mode driver Stephen Hemminger
2015-06-16 23:51 ` [dpdk-dev] [PATCH 1/4] eal: provide functions to access PCI config Stephen Hemminger
2015-06-17 7:31 ` Panu Matilainen
2015-06-17 14:44 ` David Marchand
[not found] ` <513c51e29ab6449c99ae70c77e72566c@BRMWP-EXMB11.corp.brocade.com>
2015-07-09 21:08 ` Stephen Hemminger
2015-06-16 23:51 ` [dpdk-dev] [PATCH 2/4] bnx2x: driver core Stephen Hemminger
2015-06-16 23:51 ` [dpdk-dev] [PATCH 3/4] bnx2x: driver support routines Stephen Hemminger
2015-06-16 23:51 ` [dpdk-dev] [PATCH 4/4] bnx2x: enable PMD build Stephen Hemminger
2015-06-17 11:19 ` Yotam Rubin [this message]
2015-06-26 0:57 ` [dpdk-dev] [PATCH 0/4 v5] bnx2x: poll mode driver Harish Patil
2015-07-02 12:53 ` Thomas Monjalon
2015-07-08 0:08 [dpdk-dev] [PATCH v3 0/4] " Stephen Hemminger
2015-07-08 0:08 ` [dpdk-dev] [PATCH 4/4] bnx2x: enable PMD build Stephen Hemminger
2015-07-09 18:15 [dpdk-dev] [PATCH v4 0/4] bnx2x: new poll mode driver Stephen Hemminger
2015-07-09 18:15 ` [dpdk-dev] [PATCH 4/4] bnx2x: enable PMD build 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='CABD4VVAOWEoN3P=ZNarGjdAwBYAaUjFz88=9kzMfkMm0DjGm+g@mail.gmail.com' \
--to=yotam@weka.io \
--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).