From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: ext4, wireless (was Re: 2.6.21-rc3-mm1)
Date: Thu, 08 Mar 2007 04:59:17 -0500 [thread overview]
Message-ID: <45EFDE75.5060905@garzik.org> (raw)
In-Reply-To: <20070307201839.6f45735b.akpm@linux-foundation.org>
Andrew Morton wrote:
> - The wireless changes in here need a lot of testers, please. It is major
> rework.
>
> Of course the config files got all changed around so `make oldconfig'
> breaks everything. I was able to get ipw2200 working after some fumbling,
> but perhaps John can tell people what has been changed in there? What has
> happened, from a big picture perspective?
The big big pictures is that Linux is getting a new wireless stack, one
that active developers seem to agree on. It /should/ support all the
old wireless-tools binaries out there, except the wext/netlink stuff
that people want to kill.
> - Re-added the ext4 development tree to the -mm lineup. It has stuff in
> it.
IMO I've been a bit disappointed at the rate of development. I had
hoped that patches to ext4 would be making it into mainline more rapidly.
Jeff
next prev parent reply other threads:[~2007-03-08 9:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 4:18 2.6.21-rc3-mm1 Andrew Morton
2007-03-08 9:59 ` Jeff Garzik [this message]
2007-03-08 14:50 ` 2.6.21-rc3-mm1 John W. Linville
2007-03-08 16:37 ` 2.6.21-rc3-mm1 Dave Jones
2007-03-08 17:56 ` 2.6.21-rc3-mm1 Valdis.Kletnieks
2007-03-08 18:34 ` 2.6.21-rc3-mm1 John W. Linville
2007-03-08 20:27 ` 2.6.21-rc3-mm1 Valdis.Kletnieks
2007-03-08 20:50 ` 2.6.21-rc3-mm1 Michal Piotrowski
2007-03-10 2:18 ` 2.6.21-rc3-mm1 Andrew Morton
2007-03-10 15:45 ` 2.6.21-rc3-mm1 Paul E. McKenney
[not found] ` <6bffcb0e0703111002t75a8ac51vcce7d52684e04a9d@mail.gmail.com>
2007-03-12 4:41 ` 2.6.21-rc3-mm1 Paul E. McKenney
2007-03-09 11:40 ` 2.6.21-rc3-mm1 Frederik Deweerdt
2007-03-15 9:22 ` ipw2200: can't load firmware (was Re: 2.6.21-rc3-mm1) Frederik Deweerdt
2007-03-10 8:33 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-10 8:48 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-10 8:58 ` 2.6.21-rc3-mm1 Andrew Morton
2007-03-10 9:18 ` 2.6.21-rc3-mm1 Greg KH
2007-03-10 12:43 ` 2.6.21-rc3-mm1 Jiri Kosina
2007-03-10 15:36 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-10 16:00 ` [linux-usb-devel] 2.6.21-rc3-mm1 Alan Stern
2007-03-10 16:36 ` Mariusz Kozlowski
2007-03-10 19:02 ` Alan Stern
2007-03-12 20:50 ` Mariusz Kozlowski
2007-03-12 20:53 ` Jiri Kosina
2007-03-10 13:32 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-12 18:14 ` 2.6.21-rc3-mm1 Radoslaw Szkodzinski
2007-03-14 19:06 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-15 1:07 ` 2.6.21-rc3-mm1 Andrew Morton
2007-03-15 6:09 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-15 10:16 ` 2.6.21-rc3-mm1 Mel Gorman
2007-03-15 15:37 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-15 19:59 ` 2.6.21-rc3-mm1 Mel Gorman
2007-03-16 6:43 ` 2.6.21-rc3-mm1 Mariusz Kozlowski
2007-03-16 10:03 ` 2.6.21-rc3-mm1 Mel Gorman
2007-03-17 18:26 ` [PATCH] Bias the location of pages freed for min_free_kbytes in the same MAX_ORDER_NR_PAGES blocks Mel Gorman
2007-03-18 8:22 ` Andrew Morton
2007-03-18 11:35 ` Mel Gorman
2007-03-18 18:12 ` Andrew Morton
2007-03-18 19:05 ` Mel Gorman
2007-03-18 19:28 ` Andrew Morton
2007-03-18 20:08 ` Mel Gorman
2007-03-18 20:45 ` Andrew Morton
2007-03-18 22:21 ` Mel Gorman
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=45EFDE75.5060905@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.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