From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Halasa Subject: Re: why usr/include/linux/if_frad.h is required Date: Wed, 21 Jan 2009 02:06:18 +0100 Message-ID: References: <1232463174.3088.15.camel@localhost.localdomain> <1232463242.3088.16.camel@localhost.localdomain> <200901201847.03030.arnd@arndb.de> <1232495335.3123.13.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Arnd Bergmann , Ingo Molnar , Sam Ravnborg , netdev@vger.kernel.org, davem@davemloft.net, LKML To: Jaswinder Singh Rajput Return-path: In-Reply-To: <1232495335.3123.13.camel@localhost.localdomain> (Jaswinder Singh Rajput's message of "Wed\, 21 Jan 2009 05\:18\:55 +0530") Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Jaswinder Singh Rajput writes: > usr/include/linux/if_frad.h is covered with CONFIG_DLCI from many years > and no body is complaining about it so it means no body is using it. > > So should we need to drop #if / #endif pair or the whole file from > userspace. I think the file. "Empty file exported to userspace", long unused. We can also have it back there, and it being not exported is an indicator that it's not used. I guess the #ifdef __KERNEL__ can be removed, too. -- Krzysztof Halasa