All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] bnxt patches
Date: Fri, 19 Jul 2019 09:18:47 -0700	[thread overview]
Message-ID: <20190719091847.2dc5afdf@hermes.lan> (raw)
In-Reply-To: <a4b656a2-7017-6eab-6f2c-a87d6e304c52@intel.com>

On Fri, 19 Jul 2019 13:33:32 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 7/19/2019 7:18 AM, Ajit Khaparde wrote:
> > Patchset based after an earlier submission
> > https://patchwork.dpdk.org/patch/56690/
> > 
> > This set mostly contains bug fixes, an update to the bnxt.rst doc
> > and a adds a VF PCI device ID for Thor based network controller.
> > 
> > Please apply.
> > 
> > Ajit Khaparde (2):
> >   net/bnxt: remove unnecessary interrupt disable
> >   doc: update release information for bnxt
> > 
> > Kalesh AP (1):
> >   net/bnxt: add new device id
> > 
> > Lance Richardson (1):
> >   net/bnxt: disable vector mode Tx with VLAN offload
> > 
> > Rahul Gupta (1):
> >   net/bnxt: fix interrupt rearm logic
> > 
> > Santoshkumar Karanappa Rastapur (1):
> >   net/bnxt: use correct number of RSS contexts for thor
> > 
> > Stephen Hemminger (1):
> >   net/bnxt: fix receive interrupt vector
> >   
> 
> Same for this patchset, it has been sent to late in the release cycle, will be
> considered for next release.
> 
> Regards,
> ferruh

Some of these are bug fixes. They should go in.
Also, adding new device id's should always be allowed.

Ajit, could you split the set?

  reply	other threads:[~2019-07-19 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  6:18 [dpdk-dev] [PATCH 0/7] bnxt patches Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 1/7] net/bnxt: add new device id Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 2/7] net/bnxt: use correct number of RSS contexts for thor Ajit Khaparde
2019-07-19 21:38   ` Ferruh Yigit
2019-07-19  6:19 ` [dpdk-dev] [PATCH 3/7] net/bnxt: fix receive interrupt vector Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 4/7] net/bnxt: fix interrupt rearm logic Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 5/7] net/bnxt: disable vector mode Tx with VLAN offload Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 6/7] net/bnxt: remove unnecessary interrupt disable Ajit Khaparde
2019-07-19  6:19 ` [dpdk-dev] [PATCH 7/7] doc: update release information for bnxt Ajit Khaparde
2019-07-19 21:38   ` Ferruh Yigit
2019-07-19 12:33 ` [dpdk-dev] [PATCH 0/7] bnxt patches Ferruh Yigit
2019-07-19 16:18   ` Stephen Hemminger [this message]
2019-07-19 16:58     ` Ferruh Yigit
2019-07-19 21:39 ` 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=20190719091847.2dc5afdf@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.