From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Subject: 2.6.x features log
Date: Fri, 07 Jan 2005 09:34:36 -0800 [thread overview]
Message-ID: <41DEC82C.4040502@osdl.org> (raw)
I think that people really like the Dave Jones
2.5/2.6 halloween information/update. It contained a lot
of useful info in one place, with pointers to more details.
What I'm seeing (and getting a little concerned about,
although I dislike PR with a passion) is that the 2.6.x
continuous development cycle will cause us (the Linux
community) to miss logging some of these important new
features (outside of bk). Has anyone kept a track of new
features that are being added in 2.6?
I'll keep a list (or someone else can -- DaveJ ?) if anyone
is interested in feeding items into it. Or do distros
already keep such a running list of new features?
For example (and some of these might not be needed here):
- NUMA support and API, including some CPU affinity updates
- hotplug and udev
- security fixes
- better ACPI support, better interrupt routing, MSI support
- faster pipes
Thoughts?
Thanks,
--
~Randy
next reply other threads:[~2005-01-07 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 17:34 Randy.Dunlap [this message]
2005-01-07 18:46 ` 2.6.x features log jerome lacoste
2005-01-07 18:54 ` Rahul Karnik
2005-01-07 19:18 ` Diego Calleja
2005-01-08 1:54 ` Dave Jones
2005-01-09 12:18 ` Christoph Hellwig
2005-01-09 19:36 ` Dave Jones
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=41DEC82C.4040502@osdl.org \
--to=rddunlap@osdl.org \
--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