From: Zhu Yi <yi.zhu@intel.com>
To: "John W.Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: effort to merge iwl3945 into iwlagn
Date: Thu, 18 Dec 2008 11:32:13 +0800 [thread overview]
Message-ID: <1229571133.24353.21.camel@debian.sh.intel.com> (raw)
Hi John,
You may probably know we plan to merge the iwl3945 driver into iwlagn.
So we will have a single iwlagn driver supporting 3945/4965/5000/later
devices. This removes the duplication between iwl3945 and iwlagn and
should be easier to maintain in the future.
We started the merge last week and we have now queued some patches in
our GIT (branch iwl3945, patches are between upstream..iwl3945):
http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi-2.6.git;a=shortlog;h=iwl3945
All of them are code movement and no functional change.
As the .29 merge window will be closed soon and it's the holiday season,
we plan to get this done (iwl3945 will be completely removed) by .30
kernel. What do you think we should do for these patches now? Do you
want to merge them into wireless-test master or create an own branch for
it? It might bring you some burden for managing them in
wireless-testing. But we really want to avoid the patch bomb when we
submit the final patchset altogether for .30.
Thanks,
-yi
next reply other threads:[~2008-12-18 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 3:32 Zhu Yi [this message]
2008-12-18 14:30 ` effort to merge iwl3945 into iwlagn John W. Linville
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=1229571133.24353.21.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).