From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rmody@marvell.com>, dev@dpdk.org
Cc: GR-Everest-DPDK-Dev@marvell.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/6] net/bnx2x: fix eth dev MTU
Date: Mon, 15 Apr 2019 09:01:19 +0100 [thread overview]
Message-ID: <779be4ba-cc60-d35a-4203-005ccfb26d17@intel.com> (raw)
In-Reply-To: <1555033662-22935-1-git-send-email-rmody@marvell.com>
On 4/12/2019 2:47 AM, Rasesh Mody wrote:
> Fix to update eth dev MTU for jumbo frames
>
> Fixes: 540a211084a7 ("bnx2x: driver core")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-04-15 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:47 Rasesh Mody
2019-04-12 1:47 ` Rasesh Mody
2019-04-12 1:47 ` [dpdk-dev] [PATCH 2/6] net/bnx2x: fix memory leak Rasesh Mody
2019-04-12 1:47 ` Rasesh Mody
2019-04-12 1:47 ` [dpdk-dev] [PATCH 3/6] net/bnx2x: fix ramrod timeout Rasesh Mody
2019-04-12 1:47 ` Rasesh Mody
2019-04-12 1:47 ` [dpdk-dev] [PATCH 4/6] net/bnx2x: fix DMAE timeout Rasesh Mody
2019-04-12 1:47 ` Rasesh Mody
2019-04-12 1:47 ` [dpdk-dev] [PATCH 5/6] net/bnx2x: fix race for periodic flags Rasesh Mody
2019-04-12 1:47 ` Rasesh Mody
2019-04-12 1:47 ` [dpdk-dev] [PATCH 6/6] net/bnx2x: fix optic module verification Rasesh Mody
2019-04-12 1:47 ` Rasesh Mody
2019-04-15 8:01 ` Ferruh Yigit [this message]
2019-04-15 8:01 ` [dpdk-dev] [PATCH 1/6] net/bnx2x: fix eth dev MTU 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=779be4ba-cc60-d35a-4203-005ccfb26d17@intel.com \
--to=ferruh.yigit@intel.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=rmody@marvell.com \
--cc=stable@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 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).