From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Wilbert Knol <w.knol@niwa.co.nz>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: [RFC] Future of INP3 patch
Date: Tue, 30 Mar 2004 16:14:28 +0200 [thread overview]
Message-ID: <20040330141428.GA27173@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0403310016220.28083-100000@zl2bsj.ampr.org>
On Wed, Mar 31, 2004 at 12:27:33AM +1200, Wilbert Knol wrote:
> It is not a case of not caring. I haven't the guts to try the 2.6
> kernels...
>
> My experience upgrading 2.2 to 2.4 wasn't a happy one. I rely on a
> working AX25 system for my E-mail, and the current 2.4.22 kernel
> (without NETROM) is reasonably stable.
Recall for how long nobody at all was looking after that code - it's quite
amazing 2.4 was working as well as it does. Here we're trying to balance
the risk of including the patch with the advantages it's going to deliver.
> I suspect several list subscribers (those running full-service DX
> Clusters, BBS's, gateways etc etc) are in the same boat.
>
> However, if the 2.6.4 kernel with Jeroen's inp3 patches applied is OK
> for AX25, then I am quite prepared to give it a try. What is the
> verdict?
The potencial of Jeroen's patch to disturb netrom systems when enabled is
fairly low; it's zero if CONFIG_NETROM is disabled or the module not loaded.
It'll need minor changes to make it bulletproof against optimizatios of
modern compiler (the extern vs. static inline thing) but with that applied
I'm very inclined to apply it.
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2004-03-30 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 18:26 [RFC] Future of INP3 patch Jeroen Vreeken
2004-03-30 12:27 ` Wilbert Knol
2004-03-30 14:14 ` Ralf Baechle DL5RB [this message]
2004-03-30 13:35 ` Øyvind Hanssen
2004-03-30 14:21 ` Ralf Baechle DL5RB
2004-09-28 11:27 ` scc multiplier (divider) option for SCC (ISA) cards Szymon Bieganski
[not found] <1355612939-3148455801.80b07a7cbd@bliksem.vehosting.nl>
2012-12-15 23:08 ` [RFC] Future of INP3 patch Matt VK2RQ
2012-12-18 22:13 ` 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=20040330141428.GA27173@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-hams@vger.kernel.org \
--cc=w.knol@niwa.co.nz \
/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