mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: sam@ravnborg.org, kai@germaschewski.name, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add ip6_tunnel.h to headers_install
Date: Sat, 19 May 2007 14:02:28 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705191358560.13309@localhost.localdomain> (raw)
In-Reply-To: <20070519174857.GA1199@plexity.net>

On Sat, 19 May 2007, Deepak Saxena wrote:

>
> The Mobile IPv6 package (http://www.mobile-ipv6.org/software/) needs
> this header file to build the tunnelctl component. The header
> already looks sanitized so is safe to export.
>
> Signed-off-by: Deepak Saxena <dsaxena@mvista.com>
>
> ---
>
> diff --git a/include/linux/Kbuild b/include/linux/Kbuild
> index bcd01f2..e101315 100644
> --- a/include/linux/Kbuild
> +++ b/include/linux/Kbuild
> @@ -239,6 +239,7 @@ unifdef-y += ipc.h
>  unifdef-y += ipmi.h
>  unifdef-y += ipv6.h
>  unifdef-y += ipv6_route.h
> +unifdef-y += ip6_tunnel.h
>  unifdef-y += isdn.h
>  unifdef-y += isdnif.h
>  unifdef-y += isdn_divertif.h

  is there some understood standard for naming header files related to
IPv6?  currently, there are header files that start with any one of
"ip6_", "ipv6_" and "ip6t_" (although the latter looks like it's
specifically for netfilter stuff).

  is there meant to be a distinction between prefixes of "ipv6_" and
"ip6_"?

rday

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-05-19 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19 17:48 Deepak Saxena
2007-05-19 18:02 ` Robert P. J. Day [this message]
2007-05-19 18:59 ` 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=Pine.LNX.4.64.0705191358560.13309@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=dsaxena@plexity.net \
    --cc=kai@germaschewski.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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

all inboxes | Powered by JetHome®