From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] bnxt patchset
Date: Fri, 20 Apr 2018 11:20:45 +0100 [thread overview]
Message-ID: <f2299d80-968a-45a9-44a0-05a1db5ff7d9@intel.com> (raw)
In-Reply-To: <20180420040845.84616-1-ajit.khaparde@broadcom.com>
On 4/20/2018 5:08 AM, Ajit Khaparde wrote:
> Please apply.
>
> Ajit Khaparde (3):
> net/bnxt: cache address of doorbell to subsequent access
> net/bnxt: fix set_rx_mask from using invalid vnic id
> net/bnxt: fix mbuf data_off initialization
Hi Ajit,
Still getting warnings with check-git-log.sh [1], can you please check?
$ ./devtools/check-git-log.sh -3
Wrong headline format:
net/bnxt: fix set_rx_mask from using invalid vnic id
net/bnxt: fix mbuf data_off initialization
next prev parent reply other threads:[~2018-04-20 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 4:08 Ajit Khaparde
2018-04-20 4:08 ` [dpdk-dev] [PATCH v2 1/3] net/bnxt: cache address of doorbell to subsequent access Ajit Khaparde
2018-04-20 4:08 ` [dpdk-dev] [PATCH v2 2/3] net/bnxt: fix set_rx_mask from using invalid vnic id Ajit Khaparde
2018-04-20 4:08 ` [dpdk-dev] [PATCH v2 3/3] net/bnxt: fix mbuf data_off initialization Ajit Khaparde
2018-04-20 10:20 ` Ferruh Yigit [this message]
2018-04-20 10:46 ` [dpdk-dev] [PATCH v2 0/3] bnxt patchset Thomas Monjalon
2018-04-20 14:21 ` [dpdk-dev] [PATCH v3 " Ajit Khaparde
2018-04-20 14:22 ` [dpdk-dev] [PATCH v3 1/3] net/bnxt: cache address of doorbell to subsequent access Ajit Khaparde
2018-04-20 14:22 ` [dpdk-dev] [PATCH v3 2/3] net/bnxt: avoid invalid vnic id in set L2 Rx mask Ajit Khaparde
2018-04-20 14:22 ` [dpdk-dev] [PATCH v3 3/3] net/bnxt: fix mbuf data offset initialization Ajit Khaparde
2018-04-20 14:54 ` [dpdk-dev] [PATCH v3 0/3] bnxt patchset Ferruh Yigit
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=f2299d80-968a-45a9-44a0-05a1db5ff7d9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).