From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
Dekel Peled <dekelp@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@mellanox.com>,
Dekel Peled <dekelp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v5] net/mlx5: support new representor naming format
Date: Mon, 18 Mar 2019 06:59:20 +0000 [thread overview]
Message-ID: <AM0PR0502MB37954A193BB1D48B51C8FE75C3470@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190318065920.0xLXovelAyPjZEBD08ayJK5QY0VmsoHU6TpJj6_4y3k@z> (raw)
In-Reply-To: <AM4PR05MB3265E18EF97CE548BDAB7221D2470@AM4PR05MB3265.eurprd05.prod.outlook.com>
Monday, March 18, 2019 8:29 AM, Slava Ovsiienko
> Subject: RE: [dpdk-dev] [PATCH v5] net/mlx5: support new representor
> naming format
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
> > Sent: Sunday, March 17, 2019 8:23
> > To: Yongseok Koh <yskoh@mellanox.com>; Shahaf Shuler
> > <shahafs@mellanox.com>
> > Cc: dev@dpdk.org; Ori Kam <orika@mellanox.com>; Dekel Peled
> > <dekelp@mellanox.com>
> > Subject: [dpdk-dev] [PATCH v5] net/mlx5: support new representor
> > naming format
> >
> > Kernel update [1] introduce new format of representors names.
> > This patch implements RFC [2], updating MLX5 PMD to support the new
> > format, while maintaining support of the existing format.
> >
> > [1]
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> > ub
> .com%2Ftorvalds%2Flinux%2Fcommit%2Fc12ecc2&data=02%7C01%7Cvi
> > acheslavo%40mellanox.com%7C17dec02b64014892fa4a08d6aaa12e04%7Ca
> > 652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636884006586825444&a
> >
> mp;sdata=YFOOhRcJ2qb19nRUA9aRUqHP8HChHLX7VP1tlWZ5OLk%3D&
> > reserved=0
> > [2]
> >
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmails
> > .d
> > pdk.org%2Farchives%2Fdev%2F2019-
> >
> March%2F125676.html&data=02%7C01%7Cviacheslavo%40mellanox.co
> > m%7C17dec02b64014892fa4a08d6aaa12e04%7Ca652971c7d2e4d9ba6a4d14
> > 9256f461b%7C0%7C0%7C636884006586825444&sdata=EWWcj5GANyC
> > 5nKdNaCuqUeRZmXIEgH4HHRbc52h5cto%3D&reserved=0
> >
> > Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> >
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Applied to next-net-mlx, thanks.
next prev parent reply other threads:[~2019-03-18 6:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 15:25 [dpdk-dev] [PATCH] net/mlx5: support new representors' " Dekel Peled
2019-03-03 7:43 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2019-03-07 8:57 ` Shahaf Shuler
2019-03-10 14:55 ` Dekel Peled
2019-03-10 15:21 ` [dpdk-dev] [PATCH v3] net/mlx5: support new representor " Dekel Peled
2019-03-10 16:06 ` [dpdk-dev] [PATCH v4] " Dekel Peled
2019-03-17 6:23 ` [dpdk-dev] [PATCH v5] " Dekel Peled
2019-03-17 6:23 ` Dekel Peled
2019-03-18 6:29 ` Slava Ovsiienko
2019-03-18 6:29 ` Slava Ovsiienko
2019-03-18 6:59 ` Shahaf Shuler [this message]
2019-03-18 6:59 ` Shahaf Shuler
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=AM0PR0502MB37954A193BB1D48B51C8FE75C3470@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=viacheslavo@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).