From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix Tx doorbell
Date: Thu, 5 Jan 2017 17:25:04 +0100 [thread overview]
Message-ID: <20170105162504.GB20719@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <2da35386-f774-a1ca-c4f2-cc77f74f6e2c@intel.com>
On Thu, Jan 05, 2017 at 03:19:35PM +0000, Ferruh Yigit wrote:
> On 12/9/2016 1:27 PM, Nelio Laranjeiro wrote:
> > Too much data is uselessly written to the Tx doorbell.
> >
> > Fixes: 1d88ba171942 ("net/mlx5: refactor Tx data path")
> >
> > Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> > Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> >
>
> Applied to dpdk-next-net/master, thanks.
>
> Is not CC'ing stable intentional, since this patch depends on a patch
> introduced in this release? If not intentional, please CC stable.
Hi Ferruh,
It was intentional, this commit won't apply as is on stable branch.
Thanks for the remind,
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2017-01-05 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 13:27 Nelio Laranjeiro
2017-01-05 15:19 ` Ferruh Yigit
2017-01-05 16:25 ` Nélio Laranjeiro [this message]
2017-01-05 16:32 ` Adrien Mazarguil
2017-01-05 16:52 ` Adrien Mazarguil
2017-01-05 17:01 ` Ferruh Yigit
2017-01-05 18:12 ` Adrien Mazarguil
2017-01-05 18:17 ` 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=20170105162504.GB20719@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.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 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).