From: Ralf Baechle <ralf@linux-mips.org>
To: Bernard Pidoux <pidoux@ccr.jussieu.fr>
Cc: linux-hams@vger.kernel.org
Subject: Re: different AX25.H files with same names
Date: Thu, 18 May 2006 15:49:54 +0100 [thread overview]
Message-ID: <20060518144954.GA1063@linux-mips.org> (raw)
In-Reply-To: <44670260.2050105@ccr.jussieu.fr>
On Sun, May 14, 2006 at 12:11:44PM +0200, Bernard Pidoux wrote:
> 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.
> So why not rename it ax25_kernel.h
I just don't see a convcingint reason for it. If it aint broke don't
fix it. Chances are renaming will break some software which against
good advice is using the kernel header file anyway.
Ralf
next prev parent reply other threads:[~2006-05-18 14:49 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 ` different AX25.H files with same names Bernard Pidoux
2006-05-18 14:49 ` Ralf Baechle [this message]
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=20060518144954.GA1063@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-hams@vger.kernel.org \
--cc=pidoux@ccr.jussieu.fr \
/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.