From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Tatyana Nikolova
<tatyana.e.nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
e1000-rdma-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH rdma-core] qedr: Fix a wrong field in struct rdma_rq_sge
Date: Wed, 18 Jan 2017 18:19:40 +0200 [thread overview]
Message-ID: <20170118161940.GD32481@mtr-leonro.local> (raw)
In-Reply-To: <1484682252-32964-1-git-send-email-tatyana.e.nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On Tue, Jan 17, 2017 at 01:44:12PM -0600, Tatyana Nikolova wrote:
> Fixes: 13b2b3cf148c ("libqedr: fix queue wrapping logic")
>
> After enabling FP_DP_VERBOSE macro, for example:
> #define FP_DP_VERBOSE(...) DP_VERBOSE(__VA_ARGS__)
>
> libqedr compilation fails with the error below:
>
> In file included from ../providers/qedr/qelr_verbs.c:48:0:
> ../providers/qedr/qelr_verbs.c: In function ‘qelr_post_recv’:
> ../providers/qedr/qelr_verbs.c:1447:14: error: ‘struct rdma_rq_sge’ has no member named ‘first_addr’
> rqe->first_addr.hi, rqe->first_addr.lo);
>
> Signed-off-by: Tatyana Nikolova <tatyana.e.nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> ---
> providers/qedr/qelr_verbs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This fix isn't relevant anymore, Ram deleted these macros.
Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-01-18 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 19:44 [PATCH rdma-core] qedr: Fix a wrong field in struct rdma_rq_sge Tatyana Nikolova
[not found] ` <1484682252-32964-1-git-send-email-tatyana.e.nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-18 16:19 ` 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=20170118161940.GD32481@mtr-leonro.local \
--to=leonro-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=e1000-rdma-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tatyana.e.nikolova-ral2JQCrhuEAvxtiuMwx3w@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