From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 02/13] net/dpaa: fix jumbo buffer config
Date: Tue, 18 Sep 2018 16:03:29 +0200 [thread overview]
Message-ID: <4111188.BaBaHoflxE@xps> (raw)
In-Reply-To: <1537277516-8876-3-git-send-email-hemant.agrawal@nxp.com>
18/09/2018 15:31, Hemant Agrawal:
> Avoid return after the jumbo buffer config in dev config API
>
> Fixes: 9658ac3a4ef6 ("net/dpaa: set the correct frame size in device MTU")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Thanks for adding some comments in this series.
About this fix, would it be easier to understand if explaining
what is the bug first?
next prev parent reply other threads:[~2018-09-18 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1535539660-20228-2-git-send-email-hemant.agrawal@nxp.com>
[not found] ` <1537277516-8876-1-git-send-email-hemant.agrawal@nxp.com>
2018-09-18 13:31 ` Hemant Agrawal
2018-09-18 14:03 ` Thomas Monjalon [this message]
2018-09-18 16:22 ` [dpdk-stable] [dpdk-dev] " Hemant
2018-09-18 13:31 ` [dpdk-stable] [PATCH v2 04/13] net/dpaa: fix link speed based on MAC type Hemant Agrawal
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=4111188.BaBaHoflxE@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.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).