From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 00/13] bnxt atchset
Date: Wed, 10 Jan 2018 20:32:57 +0000 [thread overview]
Message-ID: <152366c7-43e4-af41-751f-02006058d0d4@intel.com> (raw)
In-Reply-To: <20180108202437.56305-1-ajit.khaparde@broadcom.com>
On 1/8/2018 8:24 PM, Ajit Khaparde wrote:
> Please apply these patches.
>
> Ajit Khaparde (10):
> net/bnxt: check return values in bnxt_dev_init
> net/bnxt: fix double increment of idx during Tx ring alloc
> net/bnxt: parse checksum offload flags
> net/bnxt: fix grp_info usage
> net/bnxt: return proper error code
> net/bnxt: add check for multi host PF per port.
> net/bnxt: check if initialization is done before accessing stats
> net/bnxt: fix check for ether_type
> net/bnxt: check on-chip resources
>
> Somnath Kotur (3):
> net/bnxt: fix duplicate filter pattern creation error
> net/bnxt: remove unnecessary addition of a temporary filter
> net/bnxt: fix bug with duplicate pattern for 5tuple filter
> bnxt/bnxt: free the aggregration ring while freeing all the HWRM rings
Series applied to dpdk-next-net/master, thanks.
Fixes lines are missing for some patches [1], can you please provide them, I can
update commits when received.
[1]
$ ./devtools/check-git-log.sh -13
Missing 'Fixes' tag:
net/bnxt: fix group info usage
net/bnxt: fix duplicate filter pattern creation error
net/bnxt: fix bug with duplicate pattern for 5tuple filter
prev parent reply other threads:[~2018-01-10 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 20:24 Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 01/13] net/bnxt: check return values in bnxt_dev_init Ajit Khaparde
2018-01-08 20:53 ` Stephen Hemminger
2018-01-08 20:24 ` [dpdk-dev] [PATCH 02/13] net/bnxt: fix double increment of idx during Tx ring alloc Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 03/13] net/bnxt: parse checksum offload flags Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 04/13] net/bnxt: fix grp_info usage Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 05/13] net/bnxt: return proper error code Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 06/13] net/bnxt: add check for multi host PF per port Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 07/13] net/bnxt: check if initialization is done before accessing stats Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 08/13] net/bnxt: fix check for ether_type Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 09/13] net/bnxt: remove unnecessary addition of a temporary filter Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 10/13] net/bnxt: fix duplicate filter pattern creation error Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 11/13] net/bnxt: fix bug with duplicate pattern for 5tuple filter Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 12/13] bnxt/bnxt: free the aggregration ring while freeing all the HWRM rings Ajit Khaparde
2018-01-08 20:24 ` [dpdk-dev] [PATCH 13/13] net/bnxt: check on-chip resources Ajit Khaparde
2018-01-10 20:32 ` Ferruh Yigit [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=152366c7-43e4-af41-751f-02006058d0d4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.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).