Note on wireless development process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Just a general note... like many other areas of the kernel, there is no wireless roadmap. There is a set of technical criteria (see '2.6.x wireless update and status' post), but there is no One True Path to follow to get there.

People interested in working on wireless need to be their own guides, and find their own path. There has been endless discussion on wireless, and not much movement. So asking questions without attaching a patch won't get very far. The general process is just like any other kernel development process: post a patch, get feedback, revise patch, lather rinse repeat.

Don't wait for DaveM or me to suddenly post reams of wireless code. I'm speculating about David's time, but I'm just too darned busy. David and I play the roles of reviewer and advisor. It's up to YOU to "scratch the itch" and get world-class wireless support into Linux.

With regards to development process, the main point of coordination is the wireless-2.6 queue itself, not a human. Look at the wireless-2.6 tree, consider what your next step is, and go there. Don't bother thinking too much about code outside that tree (and upstream).

Please direct questions and comments to the [email protected] mailing list, rather than privately emailing me or DaveM. That way knowledge is shared, debated, and archived.

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux