From: 9a4gl@9a0tcp.ampr.org (Tihomir Heidelberg)
To: cathrynm@junglevision.com
Cc: linux-hams@vger.kernel.org
Subject: Re: kernel 2.4.21 and AX25 & netrom
Date: Tue, 02 Sep 03 14:45:36 CEST [thread overview]
Message-ID: <12833@9A0TCP> (raw)
In-Reply-To: your message of Mon, 01 Sep 2003 13:29:40 -0700. <3F53AC34.7030706@junglevision.com>
> Well, thanks for working on this. So, then let me get this straight. The
> most stable option is to get 2.4.21 and patch it with your patch, and that's
> different from 2.4.22, right?
2.4.22 have one bugfix by dl9sau which fixes problem when kernel sends
SABM frames with unknown calls... didnt try, but my patch should also
apply to 2.4.22, will check in few days when will have more time, then
I will also create patch for 2.4.22...
73 de Tihomir, 9a4gl@9a0tcp.ampr.org
next prev parent reply other threads:[~2003-09-02 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 19:08 kernel 2.4.21 and AX25 & netrom Tihomir Heidelberg
2003-09-01 20:29 ` Cathryn Mataga
2003-09-02 12:45 ` Tihomir Heidelberg [this message]
2003-09-02 1:47 ` Philip Maley
-- strict thread matches above, loose matches on Subject: below --
2003-09-02 12:55 Tihomir Heidelberg
2003-08-30 15:51 Luiz Catalan
2003-09-01 8:08 ` terry
2003-09-01 13:19 ` Luiz Catalan
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=12833@9A0TCP \
--to=9a4gl@9a0tcp.ampr.org \
--cc=cathrynm@junglevision.com \
--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