All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"matthew@wil.cx" <matthew@wil.cx>
Subject: RE: [PATCH] fs.h: introduce functions to get/set file->private_data
Date: Mon, 16 Aug 2010 16:50:01 -0700	[thread overview]
Message-ID: <1282002601.6518.116.camel@Joe-Laptop> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697643E50D82E@AUSP01VMBX24.collaborationhost.net>

On Mon, 2010-08-16 at 18:36 -0500, H Hartley Sweeten wrote:
> It's just a pain trying to figure out where the file 'private_data' is being
> used.

spatch (coccinelle) could help a lot with this style problem.

For instance, here's a grep equivalent for any use
of (struct file) member private_data in directory fs

$ cat t.cocci
@@
struct file *file;
@@

* file->private_data
$ spatch -very_quiet -sp_file t.cocci fs



  reply	other threads:[~2010-08-16 23:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 18:37 [PATCH] fs.h: introduce functions to get/set file->private_data H Hartley Sweeten
2010-08-16 23:17 ` Christoph Hellwig
2010-08-16 23:36   ` H Hartley Sweeten
2010-08-16 23:50     ` Joe Perches [this message]
2010-08-17  1:03       ` Ted Ts'o
2010-08-17  1:58         ` Joe Perches
2010-08-17  8:54         ` Christoph Hellwig
2010-08-17  8:54         ` Christoph Hellwig
2010-08-17 17:26           ` Joe Perches
2010-08-17 17:58             ` Sam Ravnborg
2010-08-17 18:21               ` Joe Perches
2010-08-18  1:32               ` Joe Perches
2010-08-18 16:48                 ` H Hartley Sweeten
2010-08-18 16:48                   ` H Hartley Sweeten
2010-08-18 17:15                   ` Joe Perches

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=1282002601.6518.116.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=hartleys@visionengravers.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.