From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: [dpdk-dev] [PATCH] mlx5: fix packet padding macro check
Date: Wed, 23 Mar 2016 10:25:49 +0100 [thread overview]
Message-ID: <1458725150-13796-1-git-send-email-adrien.mazarguil@6wind.com> (raw)
All instances of HAVE_EXP_CREATE_WQ_FLAG_RX_END_PADDING were not replaced by
HAVE_VERBS_RX_END_PADDING during a rework of the original patch, effectively
preventing this feature from being used.
Fixes: 89ed2405447d ("mlx5: add support for HW packet padding")
Unfortunately I did not catch this earlier (one should avoid last minute
changes).
Bruce, since the above commit is currently only present in your tree, can
you merge this fix with it during your next rebase? I do not mind keeping
a separate fix but the commit ID will have to be updated later. Thanks.
Adrien Mazarguil (1):
mlx5: fix packet padding macro check
drivers/net/mlx5/mlx5.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-23 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 9:25 Adrien Mazarguil [this message]
2016-03-23 9:25 ` Adrien Mazarguil
2016-03-23 11:53 ` Bruce Richardson
2016-03-23 12:43 ` Adrien Mazarguil
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=1458725150-13796-1-git-send-email-adrien.mazarguil@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).