From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] rxe: expose num_possible_cpus() cnum_comp_vectors
Date: Thu, 4 May 2017 16:50:35 +0300 [thread overview]
Message-ID: <20170504135035.GW22833@mtr-leonro.local> (raw)
In-Reply-To: <1493904187-13686-1-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
On Thu, May 04, 2017 at 04:23:07PM +0300, Sagi Grimberg wrote:
> Their completely logical, so don't pose an artificial limitation.
>
> Signed-off-by: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
> ---
Thanks a lot,
Reviewed-by: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-04 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 13:23 [PATCH] rxe: expose num_possible_cpus() cnum_comp_vectors Sagi Grimberg
[not found] ` <1493904187-13686-1-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-05-04 13:50 ` Leon Romanovsky [this message]
2017-05-04 14:01 ` Moni Shoua
[not found] ` <CAG9sBKNBXkhJ9viPJ7ZMD8fEdUJ9i_c4FTVg27=GLL2SyBSM2g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-04 14:03 ` Sagi Grimberg
[not found] ` <5c52626d-3347-173e-a9f5-c1c45cafb508-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-05-04 14:16 ` Moni Shoua
[not found] ` <CAG9sBKOc6EK-qrbvFa6x7QM5ZFEvJmUXfuhRkbXNAJpi+FT_Kg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-04 14:26 ` Sagi Grimberg
[not found] ` <eeea953a-1508-d0c9-66a6-1b73e03ea80a-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-05-04 14:43 ` Moni Shoua
2017-05-04 23:47 ` 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=20170504135035.GW22833@mtr-leonro.local \
--to=leonro-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org \
/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).