netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: David Miller <davem@davemloft.net>
Cc: shemminger@vyatta.com, jaswinderlinux@gmail.com, khc@pm.waw.pl,
	jaswinder@kernel.org, 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: Thu, 22 Jan 2009 06:37:36 +0100	[thread overview]
Message-ID: <20090122053736.GA6214@uranus.ravnborg.org> (raw)
In-Reply-To: <20090121.153712.84781438.davem@davemloft.net>

On Wed, Jan 21, 2009 at 03:37:12PM -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.

Thanks for investigating David.

	Sam


  reply	other threads:[~2009-01-22  5:35 UTC|newest]

Thread overview: 15+ 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 [this message]
2009-01-24 13:25                     ` Jaswinder Singh Rajput
2009-01-24 15:32                       ` Krzysztof Halasa
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=20090122053736.GA6214@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=jaswinder@kernel.org \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).