From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: linux-hams@vger.kernel.org
Subject: different AX25.H files with same names
Date: Sun, 14 May 2006 12:11:44 +0200 [thread overview]
Message-ID: <44670260.2050105@ccr.jussieu.fr> (raw)
In-Reply-To: <20060513144258.GA3640@linux-mips.org>
Ralf Baechle DL5RB wrote :
> On Sat, May 13, 2006 at 02:31:11PM +0200, Bernard Pidoux wrote:
>
>> By the way, its a long time since I want to ask if there is any reason
>> to keep the same name for different ax25.h include files.
>>
>> /usr/include/netax25/ax25.h
>> /usr/src/linux/include/linux/ax25.h
>> /usr/src/linux/include/net/ax25.h
>>
>> Somehow it may be confusing.
>
> One for building applications, one for the kernel itself.
>
> 73 de DL5RB op Ralf
>
> --
> Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
I understand that these files have different usage.
This is why I think that they should have different names.
Here is the content of /usr/src/linux/include/linux/ax25.h
----------------
/*
* These are the public elements of the Linux kernel AX.25 code. A similar
* file netrom.h exists for the NET/ROM protocol.
*/
#ifndef AX25_KERNEL_H
#define AX25_KERNEL_H
----------------
So why not rename it ax25_kernel.h
73 de Bernard, f6bvp
http://f6bvp.org
http://rose.fpac.free.fr/MINI-HOWTO/
http://rose.fpac.free.fr/MINI-HOWTO-FR/
next prev parent reply other threads:[~2006-05-14 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 22:38 AX.25, NETROM and ROSE changes in 2.6.17 Ralf Baechle DL5RB
2006-05-06 23:16 ` ax25-tools-0.0.8src.tgz Jose Ng Lee
2006-05-07 2:25 ` ax25-tools-0.0.8src.tgz Ralf Baechle DL5RB
2006-05-13 12:31 ` AX.25, NETROM and ROSE changes in 2.6.17 Bernard Pidoux
2006-05-13 14:42 ` Ralf Baechle DL5RB
2006-05-14 10:11 ` Bernard Pidoux [this message]
2006-05-18 14:49 ` different AX25.H files with same names Ralf Baechle
2006-05-18 15:06 ` Mike McCarthy, W1NR
2006-05-21 21:51 ` AX.25, NETROM and ROSE changes in 2.6.17 Bernard Pidoux
2006-05-22 0:06 ` Ralf Baechle DL5RB
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=44670260.2050105@ccr.jussieu.fr \
--to=pidoux@ccr.jussieu.fr \
--cc=linux-hams@vger.kernel.org \
--cc=ralf@linux-mips.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