All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: shemminger@vyatta.com, sam@ravnborg.org,
	jaswinderlinux@gmail.com, khc@pm.waw.pl, arnd@arndb.de,
	mingo@elte.hu, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: why usr/include/linux/if_frad.h is required
Date: Sat, 24 Jan 2009 18:55:33 +0530	[thread overview]
Message-ID: <1232803533.17900.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20090121.153712.84781438.davem@davemloft.net>

On Wed, 2009-01-21 at 15:37 -0800, David Miller wrote:
> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Wed, 21 Jan 2009 17:38:38 +1100
> 
> > There are no references if_frad.h in the version of Sangoma (out of
> > tree) code that we use in Vyatta.
> 
> frad-0.20:src/dlcicfg.c
> 
> It includes linux/if_frad.h and also performs the DLCI_SET_CONF
> ioctl.
> 
> Enough evidence to show we need to keep this header in the
> export set.  Let's just kill the bogus CONFIG_* ifdef
> tests in there.

After killing CONFIG_DLCI and CONFIG_DLCI_MODULE, it is also killing the
kernel:

  CC      net/socket.o
In file included from net/socket.c:75:
include/linux/if_frad.h:170: error: ‘CONFIG_DLCI_MAX’ undeclared here (not in a function)
make[1]: *** [net/socket.o] Error 1
make: *** [net] Error 2

because these things still depends on CONFIG_DLCI:

struct frad_local
{
   struct net_device_stats stats;

   /* devices which this FRAD is slaved to */
   struct net_device     *master[CONFIG_DLCI_MAX];
   short             dlci[CONFIG_DLCI_MAX];

Are you still sure we do not need CONFIG_DLCI.

--
JSR


  parent reply	other threads:[~2009-01-24 13:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 14:52 why usr/include/linux/if_frad.h is required Jaswinder Singh Rajput
2009-01-20 14:54 ` Jaswinder Singh Rajput
2009-01-20 17:47   ` Arnd Bergmann
2009-01-20 19:53     ` Krzysztof Halasa
2009-01-20 23:48       ` Jaswinder Singh Rajput
2009-01-21  1:06         ` Krzysztof Halasa
2009-01-21  4:50           ` Jaswinder Singh Rajput
2009-01-21  5:33             ` Sam Ravnborg
2009-01-21  6:15               ` David Miller
2009-01-21  6:38                 ` Stephen Hemminger
2009-01-21 23:37                   ` David Miller
2009-01-22  5:37                     ` Sam Ravnborg
2009-01-24 13:25                     ` Jaswinder Singh Rajput [this message]
2009-01-24 15:32                       ` Krzysztof Halasa
2009-01-26 20:30                         ` David Miller
2009-01-26 20:30                           ` David Miller

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=1232803533.17900.4.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=jaswinderlinux@gmail.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=shemminger@vyatta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.