mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: linux-kernel@vger.kernel.org
Subject: Generic HDLC update for 2.4.21-pre6, 2.4.21pre5-ac3, 2.5.66
Date: 01 Apr 2003 02:00:41 +0200	[thread overview]
Message-ID: <m3istzf5na.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <7C078C66B7752B438B88E11E5E20E72E0EF78D@GENERAL.farsite.co.uk>

Hi,

Kevin Curtis <kevin.curtis@farsite.co.uk> writes:

> Hi Marcelo,
> 	what about the Generic HDLC patch?   Please please please can we
> have it in 2.4.21?  I am sure others would like to see it there too.

I've put the updated HDLC patch (against 2.4.21pre6) in:
ftp://ftp.pm.waw.pl/pub/linux/hdlc/current/hdlc-2.4.21pre6.patch.gz

against 2.4.21-pre5-ac3:
ftp://ftp.pm.waw.pl/pub/linux/hdlc/current/hdlc-2.4.21pre5-ac3.patch.gz

against 2.5.66 (this is, of course, a little different):
ftp://ftp.pm.waw.pl/pub/linux/hdlc/current/hdlc-2.5.66.patch.gz

Tested on all hardware I've access to (C101 and N2) on 2.4 and 2.5 kernels.

No much changes from previous release (the one in Alan's 2.4 tree): my (low
level) drivers have now smaller TX packet rings to decrease TX latency for
high priority packets (LMI etc), and there is only one RAM-sizing routine
for both cards (as well as for drivers not included in the official tree).

The code has been cleaned a bit.
kmalloc(GFP_KERNEL) in interrupt context has been fixed.
Some __init etc fixes.
No ABI/API changes.

Marcelo, please apply to 2.4.21-pre6,
Alan, please apply to 2.4.21-pre5-ac3,
Linus, please apply to 2.5.66.

Thanks.
-- 
Krzysztof Halasa
Network Administrator

      reply	other threads:[~2003-03-31 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 16:58 Linux 2.4.21-pre6 Kevin Curtis
2003-04-01  0:00 ` Krzysztof Halasa [this message]

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=m3istzf5na.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®