Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S293720AbSCETAD>; Tue, 5 Mar 2002 14:00:03 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S293734AbSCES7x>; Tue, 5 Mar 2002 13:59:53 -0500
Received: from pc3-camc5-0-cust13.cam.cable.ntl.com ([80.4.125.13]:55465 "EHLO
	fenrus.demon.nl") by vger.kernel.org with ESMTP id <S293720AbSCES7l>;
	Tue, 5 Mar 2002 13:59:41 -0500
Date: Tue, 5 Mar 2002 18:57:47 GMT
Message-Id: <200203051857.g25Ivl627158@fenrus.demon.nl>
From: arjan@fenrus.demon.nl
To: Brian S Queen <bqueen@nas.nasa.gov>
cc: linux-kernel@vger.kernel.org
Subject: Re: dnotify for kernel 2.2
In-Reply-To: <200203051845.KAA16326@marcy.nas.nasa.gov>
X-Newsgroups: fenrus.linux.kernel
User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.4.9-21 (i586))
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

In article <200203051845.KAA16326@marcy.nas.nasa.gov> you wrote:
> I have been going through the trouble of adding dnotify to our 2.2
> kernel because we don't want to switch to 2.4 yet. I wonder:
> 
> How many folks are interested in dnotify for 2.2?
> 
> Is it a really bad idea?

Does the 2.4 version actually work ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/