From: Robert Love <rml@tech9.net>
To: Simon Kirby <sim@netnation.com>
Cc: linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: [FS] Why doesn't this patch work?
Date: 05 Dec 2001 18:46:21 -0500 [thread overview]
Message-ID: <1007595982.848.4.camel@phantasy> (raw)
In-Reply-To: <20011205152834.A11289@netnation.com>
In-Reply-To: <20011205152834.A11289@netnation.com>
On Wed, 2001-12-05 at 18:28, Simon Kirby wrote:
> I'm attempting to write this little dinky patch to see who calls fsync()
> or fdatasync(), but it's spitting out compiler warnings. I can't figure
> out why, though. What did I do wrong?
>
> buffer.c: In function `report_culprit':
> buffer.c:409: warning: assignment from incompatible pointer type
> buffer.c:410: warning: passing arg 2 of `d_path' from incompatible pointer type
> buffer.c:420: warning: passing arg 1 of `mntput' from incompatible pointer type
s/struct vfsmnt/struct vfsmount/
Robert Love
next prev parent reply other threads:[~2001-12-05 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 23:28 [FS] Why doesn't this patch work? Simon Kirby
2001-12-05 23:46 ` Robert Love [this message]
2001-12-06 0:08 ` Simon Kirby
2001-12-05 23:52 ` Dave Jones
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=1007595982.848.4.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@netnation.com \
--cc=viro@math.psu.edu \
/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