From: Shahaf Shuler <shahafs@mellanox.com>
To: "Shahaf Shuler" <shahafs@mellanox.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
"Yongseok Koh" <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix compilation without tunnel RSS support
Date: Tue, 15 May 2018 12:30:29 +0000 [thread overview]
Message-ID: <DB7PR05MB442628C2289BA9F37EFE89F8C3930@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <DB7PR05MB44266FCFD17E6151593B7081C39C0@DB7PR05MB4426.eurprd05.prod.outlook.com>
Monday, May 14, 2018 9:00 AM, Shahaf Shuler:
> Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix compilation without tunnel
> RSS support
>
> Sunday, May 13, 2018 4:28 PM, Xueming(Steven) Li:
> > Thanks for fixing this, one minor issue below.
> >
> > > -----Original Message-----
> > > From: Shahaf Shuler <shahafs@mellanox.com>
> > > Sent: Sunday, May 13, 2018 4:08 PM
> > > To: Nélio Laranjeiro <nelio.laranjeiro@6wind.com>; Adrien Mazarguil
> > > <adrien.mazarguil@6wind.com>; Yongseok Koh <yskoh@mellanox.com>
> > > Cc: dev@dpdk.org; Xueming(Steven) Li <xuemingl@mellanox.com>
> > > Subject: [PATCH] net/mlx5: fix compilation without tunnel RSS
> > > support
> > >
> > > IBV_RX_HASH_INNER should be referenced only when having tunnel
> > support in the Verbs headers.
> > >
> > > Fixes: 80f2d0ed7ff9 ("net/mlx5: add hardware flow debug dump")
> > > Cc: xuemingl@mellanox.com
> > >
> > > Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-05-15 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 8:07 Shahaf Shuler
2018-05-13 13:27 ` Xueming(Steven) Li
2018-05-14 6:00 ` Shahaf Shuler
2018-05-15 12:30 ` Shahaf Shuler [this message]
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=DB7PR05MB442628C2289BA9F37EFE89F8C3930@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=xuemingl@mellanox.com \
--cc=yskoh@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 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).