From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Gautam Singaraju <gsingara@uncc.edu>
Cc: "'Daniel Drake'" <dsd@gentoo.org>,
"'David Gómez'" <david@pleyades.net>,
"'Robert Love'" <rml@novell.com>,
"'John McCutchan'" <ttb@tentacle.dhs.org>,
'Linux-kernel' <linux-kernel@vger.kernel.org>
Subject: RE: Problem with inotify
Date: Mon, 04 Jul 2005 17:00:32 +0100 [thread overview]
Message-ID: <1120492832.11399.24.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <200507041555.j64FtFL4010937@ms-smtp-04-eri0.southeast.rr.com>
Gautam,
On Mon, 2005-07-04 at 11:55 -0400, Gautam Singaraju wrote:
> I had used the 2.6.12 kernel with the latest Inotify. There was no
> "I_WILL_FREE" in the any place. And, there was no problem in compilation.
Er, yes, obviously. You are not using my patch on top of inotify and
original inotify does not use I_WILL_FREE. You are answering somewhat
out of context...
> I believe Inotify is very useful and should be included in the next versions
> of the kernel. Are there any ongoing plans for this?
I cannot answer this. Robert/John? However there appear to be issues
with it at the moment (the umount problems with ntfs volumes) so
probably not quite yet unless we figure out the problems...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2005-07-04 16:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 18:18 David Gómez
2005-06-30 18:29 ` Robert Love
2005-06-30 18:38 ` David Gómez
2005-06-30 19:33 ` David Gómez
2005-06-30 20:39 ` Anton Altaparmakov
2005-06-30 20:48 ` David Gómez
2005-06-30 22:35 ` Anton Altaparmakov
2005-07-01 20:25 ` Robert Love
2005-07-02 12:54 ` David Gómez
2005-07-02 16:25 ` Robert Love
2005-07-02 9:12 ` Daniel Drake
2005-07-02 22:09 ` Anton Altaparmakov
2005-07-02 23:38 ` Daniel Drake
2005-07-03 0:08 ` Anton Altaparmakov
2005-07-03 10:34 ` Daniel Drake
2005-07-04 14:27 ` Anton Altaparmakov
2005-07-04 14:39 ` Anton Altaparmakov
2005-07-04 15:12 ` Anton Altaparmakov
2005-07-04 15:55 ` Gautam Singaraju
2005-07-04 16:00 ` Anton Altaparmakov [this message]
2005-07-04 17:57 ` Daniel Drake
2005-07-04 19:09 ` Anton Altaparmakov
2005-07-05 1:33 ` John McCutchan
2005-07-05 7:56 ` Anton Altaparmakov
2005-07-05 15:48 ` John McCutchan
2005-07-05 17:06 ` Anton Altaparmakov
2005-07-05 18:07 ` John McCutchan
2005-07-05 20:53 ` Anton Altaparmakov
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=1120492832.11399.24.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=david@pleyades.net \
--cc=dsd@gentoo.org \
--cc=gsingara@uncc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=ttb@tentacle.dhs.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
all inboxes | Powered by JetHome®