From: Krzysztof Halasa <khc@pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Subject: [PATCH] generic HDLC update for 2.5.2 - please apply
Date: 07 Jan 2002 19:57:05 +0100 [thread overview]
Message-ID: <m3pu4mgfb2.fsf@defiant.pm.waw.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Hi,
The attached file updates 2.5 generic HDLC, please apply.
The patch includes:
- new SIOCDEVICE ioctl for setting all protocol and hardware parameters
of (HDLC) network devices, instead of using PRIVATE netdev ioctls,
- the HDLC code is now split into hdlc_generic.c, hdlc_fr.c,
hdlc_cisco.c etc. files,
- all protocol parameters (timeouts etc.) are (should/aim) now configurable
via SIOCDEVICE ioctl,
- other updates and bugfixes,
- farsync update from Bob Dunlop.
The patch should apply cleanly to 2.4.17, and I expect it backported
to 2.4 (and possibly 2.2) when all drivers using it are ready.
There is binary and source incompatibility with 2.4 kernel code
- users require new sethdlc utility.
This patch prevents dscc4 driver from compiling, I assume it will be
updated shortly as well.
Thank you.
--
Krzysztof Halasa
Network Administrator
[-- Attachment #2: hdlc-2.5.1.patch.gz --]
[-- Type: application/x-gzip, Size: 35453 bytes --]
reply other threads:[~2002-01-07 19:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3pu4mgfb2.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