From: Maciej Soltysiak <solt@dns.toxicfilms.tv>
To: davej@codemonkey.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] post-halloween consolidation.
Date: Mon, 4 Aug 2003 18:53:53 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.51.0308041852110.22851@dns.toxicfilms.tv> (raw)
Hi Dave,
post-halloween contains two similar sections:
Deprecated features
~~~~~~~~~~~~~~~~~~~
and
Deprecated
~~~~~~~~~~
This patch joins these sections together.
Regards,
Maciej Soltysiak
--- post-halloween-2.5.txt 2003-08-04 18:49:17.000000000 +0200
+++ post-halloween-2.5.txt.1 2003-08-04 18:49:38.000000000 +0200
@@ -87,6 +87,15 @@
You should now use a boot loader program instead.
- Callout tty devices (/dev/cua) have been deprecated since 2.1.90pre2.
Support is now removed.
+- usbdevfs will be going away in 2.7. The same filesystem can
+ be mounted as 'usbfs' in recent 2.4 kernels, and in 2.5.52
+ and above, which is what the filesystem will furthermore be
+ known as.
+- elvtune is deprecated (as are the ioctl's it used).
+ Instead, the io scheduler tunables are exported in sysfs (see below)
+ in the /sys/block/<device>/iosched directory.
+ Jens wrote a document explaining the tunables of the new scheduler at
+ http://www.lib.uaa.alaska.edu/linux-kernel/archive/2002-Week-44/att-deadline-iosched.txt
Modules.
~~~~~~~~
@@ -887,18 +896,6 @@
- The in-kernel loopback device can now do crypto using the CryptoAPI.
May need new userspace tools.
-Deprecated.
-~~~~~~~~~~~
-- usbdevfs will be going away in 2.7. The same filesystem can
- be mounted as 'usbfs' in recent 2.4 kernels, and in 2.5.52
- and above, which is what the filesystem will furthermore be
- known as.
-- elvtune is deprecated (as are the ioctl's it used).
- Instead, the io scheduler tunables are exported in sysfs (see below)
- in the /sys/block/<device>/iosched directory.
- Jens wrote a document explaining the tunables of the new scheduler at
- http://www.lib.uaa.alaska.edu/linux-kernel/archive/2002-Week-44/att-deadline-iosched.txt
-
Ports.
reply other threads:[~2003-08-04 16:54 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=Pine.LNX.4.51.0308041852110.22851@dns.toxicfilms.tv \
--to=solt@dns.toxicfilms.tv \
--cc=davej@codemonkey.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).