netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: <sameehj@amazon.com>
Cc: brouer@redhat.com, <davem@davemloft.net>,
	<netdev@vger.kernel.org>, <dwmw@amazon.com>, <zorik@amazon.com>,
	<matua@amazon.com>, <saeedb@amazon.com>, <msw@amazon.com>,
	<aliguori@amazon.com>, <nafea@amazon.com>, <gtzalik@amazon.com>,
	<netanel@amazon.com>, <alisaidi@amazon.com>, <benh@amazon.com>,
	<akiyano@amazon.com>, <ndagan@amazon.com>
Subject: Re: [PATCH V2 net 0/2] Fix xdp in ena driver
Date: Thu, 4 Jun 2020 11:24:04 +0200	[thread overview]
Message-ID: <20200604112404.05cdc073@carbon> (raw)
In-Reply-To: <20200603085023.24221-1-sameehj@amazon.com>

On Wed, 3 Jun 2020 08:50:21 +0000
<sameehj@amazon.com> wrote:

> From: Sameeh Jubran <sameehj@amazon.com>
> 
> This patchset includes 2 XDP related bug fixes
> 
> Difference from v1:
> * Fixed "Fixes" tag
> 
> Sameeh Jubran (2):
>   net: ena: xdp: XDP_TX: fix memory leak
>   net: ena: xdp: update napi budget for DROP and ABORTED
> 
>  drivers/net/ethernet/amazon/ena/ena_netdev.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

LGTM

Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer


  parent reply	other threads:[~2020-06-04  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  8:50 [PATCH V2 net 0/2] Fix xdp in ena driver sameehj
2020-06-03  8:50 ` [PATCH V2 net 1/2] net: ena: xdp: XDP_TX: fix memory leak sameehj
2020-06-03  8:50 ` [PATCH V2 net 2/2] net: ena: xdp: update napi budget for DROP and ABORTED sameehj
2020-06-04  3:12 ` [PATCH V2 net 0/2] Fix xdp in ena driver Jakub Kicinski
2020-06-04  9:24 ` Jesper Dangaard Brouer [this message]
2020-06-04 22:43 ` David Miller

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=20200604112404.05cdc073@carbon \
    --to=brouer@redhat.com \
    --cc=akiyano@amazon.com \
    --cc=aliguori@amazon.com \
    --cc=alisaidi@amazon.com \
    --cc=benh@amazon.com \
    --cc=davem@davemloft.net \
    --cc=dwmw@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=matua@amazon.com \
    --cc=msw@amazon.com \
    --cc=nafea@amazon.com \
    --cc=ndagan@amazon.com \
    --cc=netanel@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedb@amazon.com \
    --cc=sameehj@amazon.com \
    --cc=zorik@amazon.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 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).