From: Ralf Baechle DO1GRB <ralf@uni-koblenz.de>
To: Iain Young - G7III <g7iii@g7iii.demon.co.uk>
Cc: linux-hams@vger.kernel.org
Subject: Re: KJD 2.3.9 patch on 2.5.29
Date: Fri, 2 Aug 2002 02:32:37 +0200 [thread overview]
Message-ID: <20020802023237.B28097@dea.linux-mips.net> (raw)
In-Reply-To: <20020801194618.GA722@columbia.g7iii.bogus>; from g7iii@g7iii.demon.co.uk on Thu, Aug 01, 2002 at 08:46:18PM +0100
On Thu, Aug 01, 2002 at 08:46:18PM +0100, Iain Young - G7III wrote:
> With the AX25 status on 2.5/2.6 thread, and Tomi mentioning the
> KJD patch, I decided to see how much work would be involved in
> porting it to 2.5
>
> (since the AX25 stack hasn't been touched much for a while, I
> thought it would be easier than other subsystems, that have had
> constant change).
Definately not. The whole AX.25, NET/ROM and ROSE code is suffering from
severe bitrot. None of the internal data structures are properly locked
etc. I'm currently working on that.
So you may find it easy to get old code into the current kerrnel - but
then it'll suffer from the same problems. The fact is that the AX.25
code is looking like it was written for a 2.0 or 2.2 kernel ...
73 de DO1GRB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2002-08-02 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 19:46 KJD 2.3.9 patch on 2.5.29 Iain Young - G7III
2002-08-01 21:33 ` Hans-Peter Zorn
2002-08-02 18:38 ` Iain Young - G7III
2002-08-02 0:32 ` Ralf Baechle DO1GRB [this message]
2002-08-02 18:28 ` Iain Young - G7III
2002-08-05 12:28 ` Ralf Baechle DO1GRB
2002-08-05 17:19 ` Iain Young - G7III
2002-08-05 18:16 ` Ralf Baechle DO1GRB
2002-08-05 19:16 ` Ralf Baechle DO1GRB
2002-09-12 17:41 ` Joaquin Seoane
2002-10-01 11:39 ` KJD 2.3.9 patch on 2.5.29 (NOT FOUND) Joaquin Seoane
2002-08-05 18:02 ` KJD 2.3.9 patch on 2.5.29 Ray Heasman
2002-08-05 19:11 ` Ralf Baechle DO1GRB
2002-08-05 19:35 ` M Taylor
2002-08-06 10:22 ` Ralf Baechle DO1GRB
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=20020802023237.B28097@dea.linux-mips.net \
--to=ralf@uni-koblenz.de \
--cc=g7iii@g7iii.demon.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox