From: Robert Love <rml@novell.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@osdl.org, John McCutchan <ttb@tentacle.dhs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] inotify for 2.6.11-mm1, updated
Date: Mon, 07 Mar 2005 23:50:36 -0500 [thread overview]
Message-ID: <1110257436.12936.65.camel@localhost> (raw)
In-Reply-To: <20050308044009.GA352@infradead.org>
On Tue, 2005-03-08 at 04:40 +0000, Christoph Hellwig wrote:
> Why do you need the classdevice? I'm really not too eager about adding
> tons of new misdevices now that we can route directly to individual majors
> with cdev_add & stuff. Especially when you're actually relying on class
> device you should have your own one instead of relying on an onsolete
> layer.
We have sysfs knobs and /sys/class/misc/inotify makes sense.
> Actually, you fixed that in read_write.c, just compat.c is still missing.
> Looks like you forget to fix that one and didn't have a chance to compile-test
> the 32bit compat layer?
Yah, I just missed it. It is fixed in my tree.
Thanks,
Robert Love
next prev parent reply other threads:[~2005-03-08 4:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 18:37 [patch] inotify for 2.6.11 Robert Love
2005-03-04 19:11 ` [patch] inotify for 2.6.11-mm1 Robert Love
2005-03-07 1:19 ` Christoph Hellwig
2005-03-07 1:38 ` Andrew Morton
2005-03-07 21:27 ` [patch] inotify for 2.6.11-mm1, updated Robert Love
2005-03-08 4:40 ` Christoph Hellwig
2005-03-08 4:50 ` Robert Love [this message]
2005-03-08 17:08 ` Robert Love
2005-03-04 21:38 ` [patch] inotify for 2.6.11 Timothy R. Chavez
2005-03-04 21:40 ` Robert Love
2005-03-06 0:04 ` Christoph Hellwig
2005-03-06 0:40 ` Robert Love
2005-03-07 1:23 ` Christoph Hellwig
2005-03-07 4:33 ` Robert Love
2005-03-07 21:25 ` [patch] inotify for 2.6.11, updated Robert Love
2005-04-05 7:58 ` [patch] inotify for 2.6.11 Prakash Punnoor
2005-04-05 16:12 ` Robert Love
2005-04-05 17:20 ` Prakash Punnoor
2005-04-05 17:35 ` Robert Love
2005-04-05 22:09 ` Robert Love
2005-04-06 3:21 ` Adam Kropelin
2005-04-10 16:16 ` Erik Meitner
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=1110257436.12936.65.camel@localhost \
--to=rml@novell.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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