All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Henrique Oliveira <henrique2.gobbi@cyclades.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Kevin Curtis <kevin.curtis@farsite.co.uk>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Why is generic hldc beig ignored?   RE:Linux 2.4.22-pre4
Date: 11 Jul 2003 20:05:25 +0200	[thread overview]
Message-ID: <m3isq9djmi.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <20030711172747.GK2210@gtf.org>

Jeff Garzik <jgarzik@pobox.com> writes:

> New HDLC stuff (already in 2.5) was also developed for 2.4.  It changes
> the 2.4 HDLC userland ABI... but pretty much everybody who still
> cares about HDLC is using the new (changed) ABI.

Precisely. Still, the old HDLC is now a history, 2.4.21 contains the new
ABI/API. It's just missing some regular updates (not breaking the ABI).
-- 
Krzysztof Halasa
Network Administrator

  reply	other threads:[~2003-07-11 19:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 15:38 Why is generic hldc beig ignored? RE:Linux 2.4.22-pre4 Kevin Curtis
2003-07-10 17:11 ` Marcelo Tosatti
2003-07-10 18:39   ` Henrique Oliveira
2003-07-11  9:12     ` Alan Cox
2003-07-11 16:55       ` Henrique Oliveira
2003-07-11 17:18         ` Marcelo Tosatti
2003-07-11 17:27           ` Jeff Garzik
2003-07-11 18:05             ` Krzysztof Halasa [this message]
2003-07-11 18:00       ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2003-07-11  8:30 Kevin Curtis
     [not found] <20030711212551.A25528@electric-eye.fr.zoreil.com>
2003-07-14 11:36 ` Frantisek Rysánek
2003-07-14 12:27   ` Francois Romieu
2003-07-14 13:16   ` Krzysztof Halasa

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=m3isq9djmi.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=henrique2.gobbi@cyclades.com \
    --cc=jgarzik@pobox.com \
    --cc=kevin.curtis@farsite.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.