All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/5] bnxt patchset
Date: Thu, 02 Aug 2018 12:16:48 +0200	[thread overview]
Message-ID: <1856562.7a6bktJvQT@xps> (raw)
In-Reply-To: <20180726011548.97788-1-ajit.khaparde@broadcom.com>

26/07/2018 03:15, Ajit Khaparde:
> This patchset against next-net fixes issues identified during QA testing.
> Please apply.
> 
> Ajit Khaparde (4):
>   net/bnxt: fix to free allocated memory
>   net/bnxt: fix to release lock when alloc fails in NVM write
>   net/bnxt: check access denied error for HWRM commands
>   net/bnxt: fix to set proper reta size
> 
> Somnath Kotur (1):
>   net/bnxt: fix to remove element from the vnic's filter list

Applied with following titles (hopefully easier to read):

	net/bnxt: fix filter freeing
	net/bnxt: fix memory leaks in NVM commands
	net/bnxt: fix lock release on NVM write failure
	net/bnxt: check access denied for HWRM commands
	net/bnxt: fix RETA size

The Signed-off-by is also moved before Reviewed-by
in order to reflect the chronological order.

  parent reply	other threads:[~2018-08-02 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  1:15 [PATCH 0/5] bnxt patchset Ajit Khaparde
2018-07-26  1:15 ` [PATCH 1/5] net/bnxt: fix to remove element from the vnic's filter list Ajit Khaparde
2018-07-26  1:15 ` [PATCH 2/5] net/bnxt: fix to free allocated memory Ajit Khaparde
2018-07-26  1:15 ` [PATCH 3/5] net/bnxt: fix to release lock when alloc fails in NVM write Ajit Khaparde
2018-07-26  1:15 ` [PATCH 4/5] net/bnxt: check access denied error for HWRM commands Ajit Khaparde
2018-07-26  1:15 ` [PATCH 5/5] net/bnxt: fix to set proper reta size Ajit Khaparde
2018-08-02 10:16 ` Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-22  6:20 [PATCH 0/5] bnxt patchset Ajit Khaparde
2016-08-15 23:06 Ajit Khaparde

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=1856562.7a6bktJvQT@xps \
    --to=thomas@monjalon.net \
    --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 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.