From: David Miller <davem@davemloft.net>
To: saeedm@dev.mellanox.co.il
Cc: yuval.shaia@oracle.com, saeedm@mellanox.com, dledford@redhat.com,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
leonro@mellanox.com, eli@mellanox.com, matanb@mellanox.com,
leon@kernel.org
Subject: Re: [for-next V2 06/10] net/mlx5: Add interface to get reference to a UAR
Date: Mon, 09 Jan 2017 11:06:59 -0500 (EST) [thread overview]
Message-ID: <20170109.110659.716571071495768364.davem@davemloft.net> (raw)
In-Reply-To: <CALzJLG92QPFG8BmQU3DAvqZ7zrqurkBEDPy4O-jZSMeH0jNPFQ@mail.gmail.com>
From: Saeed Mahameed <saeedm@dev.mellanox.co.il>
Date: Mon, 9 Jan 2017 18:05:16 +0200
> I just thought that this pull request is sitting in the mailing list
> for too long and we need to move on.
Nobody reviewed it for any element of it's substance, and we had an
intervening weekend.
It did not sit for too long but any measure whatsoever.
next prev parent reply other threads:[~2017-01-09 16:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 15:54 [for-next V2 00/10][pull request] Mellanox 100G mlx5 4K UAR support Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 02/10] IB/mlx5: Fix error handling order in create_kernel_qp Saeed Mahameed
[not found] ` <1483890891-8767-1-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-01-08 15:54 ` [for-next V2 01/10] IB/mlx5: Fix kernel to user leak prevention logic Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 03/10] mlx5: Fix naming convention with respect to UARs Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 04/10] IB/mlx5: Fix retrieval of index to first hi class bfreg Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 05/10] net/mlx5: Introduce blue flame register allocator Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 06/10] net/mlx5: Add interface to get reference to a UAR Saeed Mahameed
2017-01-08 17:05 ` Yuval Shaia
[not found] ` <20170108170539.GA6323-Hxa29pjIrETlQW142y8m19+IiqhCXseY@public.gmane.org>
2017-01-09 8:31 ` Saeed Mahameed
[not found] ` <CALzJLG-yiZfa6J0WciFPowfF2LWrXAqCKc4ETu4x=ZJdn+CfDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-09 15:47 ` David Miller
[not found] ` <20170109.104722.2246652236667186272.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-01-09 16:05 ` Saeed Mahameed
2017-01-09 16:06 ` David Miller [this message]
2017-01-08 15:54 ` [for-next V2 08/10] IB/mlx5: Allow future extension of libmlx5 input data Saeed Mahameed
[not found] ` <1483890891-8767-9-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-01-10 4:24 ` Doug Ledford
2017-01-08 15:54 ` [for-next V2 07/10] IB/mlx5: Use blue flame register allocator in mlx5_ib Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 09/10] IB/mlx5: Support 4k UAR for libmlx5 Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 10/10] net/mlx5: Activate support for 4K UARs Saeed Mahameed
2017-01-10 4:29 ` [for-next V2 00/10][pull request] Mellanox 100G mlx5 4K UAR support Doug Ledford
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=20170109.110659.716571071495768364.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
--cc=yuval.shaia@oracle.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).