From: Leon Romanovsky <leonro@mellanox•com>
To: Doug Ledford <dledford@redhat•com>, Jason Gunthorpe <jgg@mellanox•com>
Cc: Moni Shoua <monis@mellanox•com>,
RDMA mailing list <linux-rdma@vger•kernel.org>,
Saeed Mahameed <saeedm@mellanox•com>,
linux-netdev <netdev@vger•kernel.org>
Subject: Re: [PATCH mlx5-next] net/mlx5: Separate ODP capabilities
Date: Thu, 21 Feb 2019 12:21:46 +0000 [thread overview]
Message-ID: <20190221122143.GC17501@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20190221121003.GB17501@mtr-leonro.mtl.com>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Thu, Feb 21, 2019 at 12:10:06PM +0000, Leon Romanovsky wrote:
> On Tue, Feb 19, 2019 at 03:06:37PM +0200, Leon Romanovsky wrote:
> > From: Moni Shoua <monis@mellanox•com>
> >
> > ODP support for XRC transport is not enabled by default in FW,
> > so we need separate ODP checks to enable/disable it.
> >
> > While that, rewrite the set of ODP SRQ support capabilities in way
> > that tests each field separately for clearness, which is not needed
> > for current FW, but better to have it separated.
> >
> > Signed-off-by: Moni Shoua <monis@mellanox•com>
> > Signed-off-by: Leon Romanovsky <leonro@mellanox•com>
> > ---
> > .../net/ethernet/mellanox/mlx5/core/main.c | 29 ++++++++++---------
> > 1 file changed, 15 insertions(+), 14 deletions(-)
> >
>
> Thanks, applied to mlx5-next
> f1463b9f1a97 net/mlx5: Separate ODP capabilities
>
> Doug, Jason,
>
> Can you please merge this branch into rdma-next as a preparation
> to pull request?
Sorry, it was a mistake, I dropped it.
>
> Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2019-02-21 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 13:06 [PATCH mlx5-next] net/mlx5: Separate ODP capabilities Leon Romanovsky
2019-02-21 12:10 ` Leon Romanovsky
2019-02-21 12:21 ` Leon Romanovsky [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=20190221122143.GC17501@mtr-leonro.mtl.com \
--to=leonro@mellanox$(echo .)com \
--cc=dledford@redhat$(echo .)com \
--cc=jgg@mellanox$(echo .)com \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=monis@mellanox$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeedm@mellanox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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