[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f9a31f40901202050u4b85fef2p8b9848b865c4fda0@mail.gmail.com>
Date: Wed, 21 Jan 2009 10:20:17 +0530
From: Jaswinder Singh Rajput <jaswinderlinux@...il.com>
To: Krzysztof Halasa <khc@...waw.pl>
Cc: Jaswinder Singh Rajput <jaswinder@...nel.org>,
Arnd Bergmann <arnd@...db.de>, Ingo Molnar <mingo@...e.hu>,
Sam Ravnborg <sam@...nborg.org>, netdev@...r.kernel.org,
davem@...emloft.net, LKML <linux-kernel@...r.kernel.org>
Subject: Re: why usr/include/linux/if_frad.h is required
On Wed, Jan 21, 2009 at 6:36 AM, Krzysztof Halasa <khc@...waw.pl> wrote:
> Jaswinder Singh Rajput <jaswinder@...nel.org> 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.
I will definately define #ifdef __KERNEL__ but I am also curious after
defining it there is no point of making empty
usr/include/linux/if_frad.h
--
JSR
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists