On Fri, Oct 1, 2010 at 2:42 PM, Compat-wireless cronjob account <compat@xxxxxxxxxxxxx> wrote: > > compat-wireless code metrics > > Â Â747282 - Total upstream lines of code being pulled > Â Â Â2153 - backport code changes > Â Â Â1902 - backport code additions > Â Â Â 251 - backport code deletions > Â Â Â6242 - backport from compat module > Â Â Â8395 - total backport code > Â Â1.1234 - % of code consists of backport work > Â Â Â 128 - Code changes posted but not yet merged > Â Â Â Â95 - Code additions posted but not yet merged > Â Â Â Â33 - Code deletions posted but not yet merged > Â Â0.0171 - % of code not yet merged > Â Â Â1219 - Crap changes not yet posted > Â Â Â1181 - Crap additions not yet posted > Â Â Â Â38 - Crap deletions not yet posted > Â Â0.1631 - % of crap code > > Base tree: linux-next.git > Base tree version: next-20101001 > compat-wireless release: compat-wireless-2010-10-01-6-g6d8961c-pc The e-mail always send the code-metrics of the -pc release, but note that there is also a -p release that does not have the crap/ patches applied. This is what we want for testing carl9170. Senthil, please consider using this tarball for testing carl9170: http://www.orbit-lab.org/kernel/compat-wireless-2.6/2010/10/compat-wireless-2010-10-01-p.tar.bz2 sha1sum: 5ee396743482e8573a0b6eea33eabf0f532d995b It has the following patches cherry picked from the mailing list into linux-next-pending/ directory as the assumption is they will make it into 2.6.37: mcgrof@tux ~/tmp/compat-wireless-2010-10-01-p $ head -10 linux-next-pending/*.patch ==> linux-next-pending/0001-mac80211-perform-scan-cancel-in-hw-reset-work.patch <== Reason for adding to linux-next-pending/ : On Fri, Oct 01, 2010 at 05:47:53AM -0700, Christian Lamparter wrote: > Currently, everyone is waiting for: > "[PATCH 1/6] mac80211: perform scan cancel in hw reset work" > (hopefully, it fixes the dreaded ieee80211_hw_restart deadlock.) We need this for testing purposes for carl9170 which may get done this weekend. ==> linux-next-pending/0002-carl9170-support-firmware-based-rx-filter.patch <== Reason for it not being merged upstream yet: backlog. Since this will help with load and memory we want this for final testing and evaluation of the driver. >From 8f56ba52913d4260fd7148a5919d913561e62cbd Mon Sep 17 00:00:00 2001 From: Christian Lamparter <chunkeey@xxxxxxxxxxxxxx> Date: Tue, 28 Sep 2010 23:00:59 +0200 Subject: [PATCH] carl9170: support firmware-based rx filter Now, the code-metrics change a bit and the ID for this release does as well: mcgrof@tux ~/tmp/compat-wireless-2010-10-01-p $ cat code-metrics.txt compat-wireless code metrics 747282 - Total upstream lines of code being pulled 2153 - backport code changes 1902 - backport code additions 251 - backport code deletions 6242 - backport from compat module 8395 - total backport code 1.1234 - % of code consists of backport work 128 - Code changes posted but not yet merged 95 - Code additions posted but not yet merged 33 - Code deletions posted but not yet merged 0.0171 - % of code not yet merged Base tree: linux-next.git Base tree version: next-20101001 compat-wireless release: compat-wireless-2010-10-01-6-g6d8961c-p I've test-compiled this release with `./scripts/driver-select carl9170` against 2.6.32. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
