From: Shahaf Shuler <shahafs@mellanox.com>
To: Ori Kam <orika@mellanox.com>, Matan Azrad <matan@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: update counter API for upstream
Date: Tue, 2 Apr 2019 05:32:55 +0000 [thread overview]
Message-ID: <AM0PR0502MB3795BB644BF9634FA51D3B6AC3560@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <AM4PR05MB34255E0E080B176B942F0249DB560@AM4PR05MB3425.eurprd05.prod.outlook.com>
Tuesday, April 2, 2019 8:25 AM, Ori Kam:
> Subject: RE: [PATCH] net/mlx5: update counter API for upstream
>
> Hi PSB
>
> > -----Original Message-----
> > From: Shahaf Shuler
> > Sent: Tuesday, April 2, 2019 7:57 AM
> > To: Ori Kam <orika@mellanox.com>; Matan Azrad
> <matan@mellanox.com>;
> > Yongseok Koh <yskoh@mellanox.com>
> > Cc: dev@dpdk.org
> > Subject: RE: [PATCH] net/mlx5: update counter API for upstream
> >
> > Hi Ori,
> >
> > Monday, April 1, 2019 6:28 PM, Ori Kam:
> > > Subject: [PATCH] net/mlx5: update counter API for upstream
> >
> > This is not an update, this is a fix.
>
> The reason that I don't think this is a fix since in the original commit it was
> stated that it is only for OFED 4.5 and in this case it is correct OFED changed
> the API. It is not an issue with the original commit.
It is an issue w/ the previous commit, since it should not be accepted in first place since it reference APIs which are not upstream.
next prev parent reply other threads:[~2019-04-02 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 15:27 Ori Kam
2019-04-01 15:27 ` Ori Kam
2019-04-02 4:56 ` Shahaf Shuler
2019-04-02 4:56 ` Shahaf Shuler
2019-04-02 5:24 ` Ori Kam
2019-04-02 5:24 ` Ori Kam
2019-04-02 5:32 ` Shahaf Shuler [this message]
2019-04-02 5:32 ` 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=AM0PR0502MB3795BB644BF9634FA51D3B6AC3560@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=orika@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).