From: Michael Wu <flamingice@sourmilk.net>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: Daniel Drake <dsd@gentoo.org>,
netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>,
Luis Rodriguez <mcgrof@gmail.com>
Subject: Re: zd1211 ported to Devicescape stack
Date: Sat, 2 Dec 2006 13:32:28 -0500 [thread overview]
Message-ID: <200612021332.33255.flamingice@sourmilk.net> (raw)
In-Reply-To: <20061202175737.GA5577@p15091797.pureserver.info>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Saturday 02 December 2006 12:57, Ulrich Kunitz wrote:
> I intend to track the d80211 stack, care for the forward porting
> and see also a number of things, which should be done for d80211.
>
> - 802.11a support
> - better d80211 integration (d80211_tx_status, led stuff)
> - cleanups
>
Great! I expected to handle the patch porting alone, but it's better to have
someone used to this hardware doing this.
> This will make the d80211 driver the development branch and the
> mainline driver the maintenance branch. As already stated I intend
> care for forwardportsi of the mainline fixes, but IMHO we should
> not care to much for backports and backport compatibility.
I avoided cleanups in the patch to make any patch porting from the mainline
driver easier, but if it's okay with you, I might make a few zd1211-d80211
specific clean up patches.
Thanks,
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-02 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 8:16 zd1211 ported to Devicescape stack Michael Wu
2006-12-02 13:25 ` Ulrich Kunitz
2006-12-02 14:54 ` Michael Wu
2006-12-02 15:58 ` Daniel Drake
2006-12-02 17:57 ` Ulrich Kunitz
2006-12-02 18:32 ` Michael Wu [this message]
2006-12-02 18:55 ` Daniel Drake
2006-12-02 19:53 ` Ulrich Kunitz
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=200612021332.33255.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=dsd@gentoo.org \
--cc=kune@deine-taler.de \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=netdev@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).