All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <gerlitz.or@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Or Gerlitz <ogerlitz@mellanox.com>,
	"David S. Miller" <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Eran Ben Elisha <eranbe@mellanox.com>,
	Yishai Hadas <yishaih@mellanox.com>,
	Saeed Mahameed <saeedm@mellanox.com>
Subject: Re: [PATCH net 4/4] net/mlx4_en: Split SW RX dropped counter per RX ring
Date: Thu, 21 Apr 2016 07:52:43 +0300	[thread overview]
Message-ID: <CAJ3xEMgyAyp+2g+b1wEGGVGSWMwf8CGSCmRZLBMztTRVHKcgfA@mail.gmail.com> (raw)
In-Reply-To: <1461200550.7627.1.camel@edumazet-glaptop3.roam.corp.google.com>

On Thu, Apr 21, 2016 at 4:02 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2016-04-20 at 18:00 +0300, Or Gerlitz wrote:

>> Just to be sure, you'd like me to re-spin this and fix the reporter name?

> Absolutely not, I believe patchwork should handle this just fine.
> Patchwork does not understand the "Fixes:" tag yet, but Reported-by: is
> fine.

OK, Eric and Florian, thanks for clarifying this out.

Or.

  reply	other threads:[~2016-04-21  4:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 13:01 [PATCH net 0/4] Mellaox 40G driver fixes for 4.6-rc Or Gerlitz
2016-04-20 13:01 ` [PATCH net 1/4] net/mlx4_core: Implement pci_resume callback Or Gerlitz
2016-04-20 13:01 ` [PATCH net 2/4] net/mlx4_core: Avoid repeated calls to pci enable/disable Or Gerlitz
2016-04-20 13:01 ` [PATCH net 3/4] net/mlx4_core: Don't allow to VF change global pause settings Or Gerlitz
2016-04-20 13:01 ` [PATCH net 4/4] net/mlx4_en: Split SW RX dropped counter per RX ring Or Gerlitz
2016-04-20 14:56   ` Eric Dumazet
2016-04-20 15:00     ` Or Gerlitz
2016-04-20 18:05       ` Florian Fainelli
2016-04-21  1:02       ` Eric Dumazet
2016-04-21  4:52         ` Or Gerlitz [this message]
2016-04-21 19:03 ` [PATCH net 0/4] Mellaox 40G driver fixes for 4.6-rc 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=CAJ3xEMgyAyp+2g+b1wEGGVGSWMwf8CGSCmRZLBMztTRVHKcgfA@mail.gmail.com \
    --to=gerlitz.or@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eranbe@mellanox.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=saeedm@mellanox.com \
    --cc=yishaih@mellanox.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.