From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH 0/4 v5] bnx2x: poll mode driver
Date: Thu, 02 Jul 2015 14:53:55 +0200 [thread overview]
Message-ID: <1900222.tNFK0Pm7Pr@xps13> (raw)
In-Reply-To: <D1B1F14C.91D1C%harish.patil@qlogic.com>
2015-06-26 00:57, Harish Patil:
>
> >From: Stephen Hemminger <shemming@brocade.com>
> >
> >Changes since last time:
> > 1. Support pci_config on BSD. Although since BSD probably doesn't
> > have same filesystem (/lib/firmware) the driver won't work.
> > 2. Change location of driver to match new filesystem hierarchy
> >
> >Stephen Hemminger (4):
> > eal: provide functions to access PCI config
> > bnx2x: driver core
> > bnx2x: driver support routines
> > bnx2x: enable PMD build
>
> Acked-by: Harish Patil <harish.patil@qlogic.com>
There are some comments to address.
Please Stephen, could you reply to comments *and* submit a new version?
Note: in order to ease patch management, the version number (v5 here)
must be in each patch and not only cover letter.
As explained in http://dpdk.org/dev#send,
the option --subject-prefix 'PATCH v6' would help.
prev parent reply other threads:[~2015-07-02 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 23:51 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
2015-06-26 0:57 ` [dpdk-dev] [PATCH 0/4 v5] bnx2x: poll mode driver Harish Patil
2015-07-02 12:53 ` Thomas Monjalon [this message]
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=1900222.tNFK0Pm7Pr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--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).