From: Yuval Shaia <yuval.shaia@oracle.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Saar Amar <saaramar5@gmail.com>, Li Qiang <liq3ea@163.com>,
yuval.shaia@oracle.com
Subject: Re: [Qemu-devel] [PATCH 4/5] pvrdma: release ring object in case of an error
Date: Wed, 12 Dec 2018 20:08:04 +0200 [thread overview]
Message-ID: <20181212180804.GF5747@lap1> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1812121253200.10904@xnncv>
On Wed, Dec 12, 2018 at 03:09:19PM +0530, P J P wrote:
> +-- On Wed, 12 Dec 2018, P J P wrote --+
> | | Also, can you rebase this patch on top of the patchset i posted last week:
> | | https://patchwork.kernel.org/patch/10705439/
> |
> | Okay, I'll send revised patch set. Thanks so much for the prompt review.
>
> I tried to git apply above patch-set over v3.1.0-rc2, v3.1.0-rc0, v3.0.0. But
> it does not seem to apply cleanly.
>
> ===
> $ git branch rdma v3.1.0-rc0
Can you try master?
I just did a rebase on top of master and had no conflicts.
> $ git checkout rdma
> Switched to branch 'rdma'
> $ git apply --check /tmp/add-support-for-RDMA-MAD.patch
> error: patch failed: Makefile.objs:1
> error: Makefile.objs: patch does not apply
> error: patch failed: hw/rdma/vmw/pvrdma_cmd.c:224
> error: hw/rdma/vmw/pvrdma_cmd.c: patch does not apply
> ===
>
> I skipped one of the makefile.objs/.json patch, applied others and then
> hand-fixed one of the patch pvrdma_cmd.c.
>
> After that when I try to build QEMU, it fails with
>
> ===
> $ ./configure --prefix=/tmp/ --enable-debug
> --target-list='x86_64-softmmu x86_64-linux-user'
> --enable-rdma --with-sdlabi=2.0
> $ make
> ../qemu/hw/rdma/rdma_backend.c:1132:5: error: implicit declaration of function
> ‘qapi_event_send_rdma_gid_status_changed’ [-Werror=implicit-function-declaration] qapi_event_send_rdma_gid_status_changed(ifname, true,
> ...
> ../qemu/hw/rdma/rdma_backend.c:22:10: fatal error: qapi/qapi-events-rdma.h: No
> such file or directory
> #include "qapi/qapi-events-rdma.h"
> ^~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> ===
>
> Not sure if other patches are required. Any idea?
>
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2018-12-12 18:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 13:26 [Qemu-devel] [PATCH 0/5] rdma: various issues in rdma/pvrdma backend P J P
2018-12-11 13:26 ` [Qemu-devel] [PATCH 1/5] rdma: check that num_sge does not exceed MAX_SGE P J P
2018-12-11 14:51 ` Yuval Shaia
2018-12-11 13:26 ` [Qemu-devel] [PATCH 2/5] pvrdma: add uar_read routine P J P
2018-12-11 15:22 ` Yuval Shaia
2018-12-12 1:22 ` 李强
2018-12-11 13:26 ` [Qemu-devel] [PATCH 3/5] pvrdma: check number of pages when creating rings P J P
2018-12-11 15:38 ` Yuval Shaia
2018-12-11 13:26 ` [Qemu-devel] [PATCH 4/5] pvrdma: release ring object in case of an error P J P
2018-12-11 16:47 ` Yuval Shaia
2018-12-11 17:22 ` Yuval Shaia
2018-12-11 20:14 ` P J P
2018-12-12 9:39 ` P J P
2018-12-12 16:52 ` Yuval Shaia
2018-12-12 18:08 ` Yuval Shaia [this message]
2018-12-12 18:37 ` P J P
2018-12-11 13:26 ` [Qemu-devel] [PATCH 5/5] pvrdma: check return value from pvrdma_idx_ring_has_ routines P J P
2018-12-11 17:17 ` Yuval Shaia
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=20181212180804.GF5747@lap1 \
--to=yuval.shaia@oracle.com \
--cc=liq3ea@163.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=saaramar5@gmail.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).