Linux-NFS Archive on lore.kernel.org
 help / color / Atom feed
From: Olga Kornievskaia <aglo@umich.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: rdma compile error
Date: Wed, 4 Dec 2019 13:12:43 -0500
Message-ID: <CAN-5tyEPhcE6NBktsqRKySyAUi6EeC_saWFH8A7tKFZ+Sb0jMg@mail.gmail.com> (raw)
In-Reply-To: <5E198AD1-41F7-4211-83CA-85680D8FB115@oracle.com>

On Wed, Dec 4, 2019 at 1:02 PM Chuck Lever <chuck.lever@oracle.com> wrote:
>
> Hi Olga-
>
> > On Dec 4, 2019, at 11:15 AM, Olga Kornievskaia <aglo@umich.edu> wrote:
> >
> > Hi Chuck,
> >
> > I git cloned your origin/cel-testing, it's on the following commit.
> > commit 37e235c0128566e9d97741ad1e546b44f324f108
> > Author: Chuck Lever <chuck.lever@oracle.com>
> > Date:   Fri Nov 29 12:06:00 2019 -0500
> >
> >    xprtrdma: Invoke rpcrdma_ep_create() in the connect worker
> >
> > And I'm getting the following compile error.
> >
> >  CC [M]  drivers/infiniband/core/cma_trace.o
> > In file included from drivers/infiniband/core/cma_trace.h:302:0,
> >                 from drivers/infiniband/core/cma_trace.c:16:
> > ./include/trace/define_trace.h:95:43: fatal error: ./cma_trace.h: No
> > such file or directory
> > #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
> >                                           ^
> > Is this known?
>
> I haven't had any complaints from lkp.
>
> f73179592745 ("RDMA/cma: Add trace points in RDMA Connection Manager")
>
> should have added drivers/infiniband/core/cma_trace.h .
>

The file "cma_trace.h" is there in the "core" directory. But for some
reason my compile expects it to be in include/trace directory (if I
were to copy it there I can compile).


>
> --
> Chuck Lever
>
>
>

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 16:15 Olga Kornievskaia
2019-12-04 18:01 ` Chuck Lever
2019-12-04 18:12   ` Olga Kornievskaia [this message]
2019-12-04 18:25     ` Chuck Lever
2019-12-04 19:09       ` Olga Kornievskaia

Reply instructions:

You may reply publically 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=CAN-5tyEPhcE6NBktsqRKySyAUi6EeC_saWFH8A7tKFZ+Sb0jMg@mail.gmail.com \
    --to=aglo@umich.edu \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.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

Linux-NFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nfs/0 linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ https://lore.kernel.org/linux-nfs \
		linux-nfs@vger.kernel.org
	public-inbox-index linux-nfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-nfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git