All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernard Pidoux F6BVP <f6bvp@free.fr>
To: linux-hams@vger.kernel.org
Subject: Re: [PATCH] ax25, netrom and rose fixes for 2.6.0
Date: Tue, 23 Dec 2003 23:10:15 +0100	[thread overview]
Message-ID: <3FE8BD47.4010108@free.fr> (raw)
In-Reply-To: <20031219234435.C211@jeroen.pe1rxq.ampr.org>


I just tried to compile FPAC 3.25 and FBB 7.04j against kernel 6.0 just 
to see how compilation would perform.
Although I was sure there would be a number of obsolete code and that 
the programs will not run.

I had to modify a few #includes.

Replacing for example

#include <linux/ax25.h> by "netax25/kernel_ax25.h"
#include <linux/rose.h> by "netax25/kernel_rose.h"
#include <linux/netrom.h> by "netax25/kernel_netrom.h"

helped the compilation.

However in kernel_ax25.h I found that
#define AX25_PIDINCL 8
that was in former ax25.h was no more defined.

I guess this was removed on purpose ?
Am I wrong ?

73 de Bernard, F6BVP

-------------------------

Jeroen Vreeken wrote:

> Hi,
> 
> These are a few fixes for bugs I encountered over the last few weeks:
> 
> - Fix some socket locking in ax25
> - Fix a waitqueue bug in ax25
> - Use sock_orphan in ax25
> - Fix a waitqueue bug in netrom
> - Fix a waitqueue bug in rose
> - Fix raw socket behaviour in ax25
> 
> Ralf, can you give your stamp of approval so Dave can apply them?
> 
> Jeroen



  parent reply	other threads:[~2003-12-23 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 22:44 [PATCH] ax25, netrom and rose fixes for 2.6.0 Jeroen Vreeken
2003-12-19 22:52 ` Ralf Baechle DO1GRB
2003-12-20  5:45   ` David S. Miller
2003-12-20 14:05     ` Jeroen Vreeken
2003-12-25  3:37       ` David S. Miller
2003-12-23 22:10 ` Bernard Pidoux F6BVP [this message]
2003-12-24 16:39   ` Jeroen Vreeken

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=3FE8BD47.4010108@free.fr \
    --to=f6bvp@free.fr \
    --cc=linux-hams@vger.kernel.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 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.