From: Christoph Hellwig <hch@infradead.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Bryan Schumaker <bjschuma@gmail.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v3 00/16] NFS add tracepoints
Date: Tue, 20 Aug 2013 23:39:58 -0700 [thread overview]
Message-ID: <20130821063958.GA3382@infradead.org> (raw)
In-Reply-To: <1377033113.21393.1.camel@leira.trondhjem.org>
On Tue, Aug 20, 2013 at 09:11:52PM +0000, Myklebust, Trond wrote:
> Hmm... Does the following patch fix the problem?
I think you just need to add this line to fs/nfs/Makefile:
ccflags-y += -I$(src) # needed for trace events
(stolen from XFS :))
next prev parent reply other threads:[~2013-08-21 6:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 19:34 [PATCH v3 00/16] NFS add tracepoints Trond Myklebust
2013-08-20 19:34 ` [PATCH v3 01/16] NFS: refactor code for calculating the crc32 hash of a filehandle Trond Myklebust
2013-08-20 19:34 ` [PATCH v3 02/16] NFS: Add event tracing for generic NFS events Trond Myklebust
2013-08-20 19:34 ` [PATCH v3 03/16] NFS: Pass in lookup flags from nfs_atomic_open to nfs_lookup Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 04/16] NFS: Add event tracing for generic NFS lookups Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 05/16] NFSv4: Add tracepoints for debugging state management problems Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 06/16] NFSv4: Add tracepoints for debugging file open Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 07/16] NFSv4: Add tracepoints for debugging file locking Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 08/16] NFSv4: Add tracepoints for debugging lookup/create operations Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 09/16] NFSv4: Add tracepoints for debugging inode manipulations Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 10/16] NFSv4: Add tracepoints for debugging rename Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 11/16] NFSv4: Add tracepoints for debugging delegations Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 12/16] NFSv4: Add tracepoints for debugging the idmapper Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 13/16] NFSv4: Add tracepoints for debugging getattr Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 14/16] NFSv4: Add tracepoints for debugging reads and writes Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 15/16] NFSv4.1: Add tracepoints for debugging layoutget/return/commit Trond Myklebust
2013-08-20 19:35 ` [PATCH v3 16/16] NFSv4.1: Add tracepoints for debugging slot table operations Trond Myklebust
2013-08-20 20:50 ` [PATCH v3 00/16] NFS add tracepoints Bryan Schumaker
2013-08-20 21:11 ` Myklebust, Trond
2013-08-21 6:39 ` Christoph Hellwig [this message]
2013-08-21 13:16 ` Myklebust, Trond
2013-08-21 13:28 ` Bryan Schumaker
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=20130821063958.GA3382@infradead.org \
--to=hch@infradead.org \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@gmail.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
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).