summaryrefslogtreecommitdiff
path: root/linux-next-pending
AgeCommit message (Collapse)Author
2012-03-12compat-wireless: refresh linux-next-pending patchesLuis R. Rodriguez
Signed-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>
2012-03-12compat-wireless: fix linux-next-pending/0002-backport-alx.patchLuis R. Rodriguez
The last hunk was must be placed in context, patch is stupid and will only accept hunks in order. Signed-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>
2012-03-12compat-wireless: backport addr_assign_type usageLuis R. Rodriguez
The alx driver uses the addr_assign_type variable from the netdev data structure which was added as of 2.6.35: mcgrof@tux ~/linux-next (git::master)$ git describe --contains c1f79426 v2.6.36-rc1~571^2~104 Although compat.git backported dev_hw_addr_random() the patch in compat.git cannot address usage of addr_assign_type and as such requires an ifdef around it. Signed-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>
2012-02-28compat-wireless: add alx Ethernet driver to linux-next-pending/Luis R. Rodriguez
This is now posted so we merge it. We can remove this once David merges the driver and it gets into linux-next.git. Signed-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>
2010-10-07compat-wireless: remove already applied patchesHauke Mehrtens
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2010-10-01compat-wireless: add rx filter carl9170 patch to linux-next-pending/Luis R. Rodriguez
This will help with load and memory. This patch seems to not be merged yet due to a backlog but we want it for testing purposes of carl9170. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-10-01compat-wireless: Add the pending mac80211 reset work patchLuis R. Rodriguez
We add the patch: mac80211: perform scan cancel in hw reset work patch to linux-next-pending/ directory because: 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. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-06-16compat-wireless: remove pending AR9003 IBSS fixLuis R. Rodriguez
Remove 0001-ath9k_hw-avoid-setting-cwmin-cwmax-to-0-for-IBSS-for.patch as it is upstream now. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-06-15compat-wireless: add one pending patch for ath9k_hw for adhoc for AR9003Luis R. Rodriguez
This is not merged yet but required for testing. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-06-15compat-wireless: remove all pending patchesLuis R. Rodriguez
These are all merged now Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-06-11compat-wireless: add new AR9003 series for pending patchesLuis R. Rodriguez
Some new AR9003 patches have been posted, merge them into the pending diretory for now until they get merged. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-06-03compat-wireless: remove all the pending patchesLuis R. Rodriguez
The merge window is over, so John just merged all of these posted pending patches. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-26compat-wireless: add pending fix patch for ath9kLuis R. Rodriguez
This adds this pending patch: From: Vasanthakumar Thiagarajan <vasanth@atheros.com> Subject: [PATCH] ath9k: Fix bug in the way "bf_tx_aborted" of struct ath_buf is used Date: Wed, 26 May 2010 19:06:53 -0700 This bug was introduced by the following commit Author: Vasanthakumar Thiagarajan <vasanth@atheros.com> Date: Thu Apr 15 17:38:46 2010 -0400 ath9k: Remove ATH9K_TX_SW_ABORTED and introduce a bool for this purpose Wrong buffer is checked for bf_tx_aborted field in ath_tx_num_badfrms(), this may result in a rate scaling with wrong feedback (number of unacked frames in this case). It is the last one in the chain of buffers for an aggregate frame that should be checked. Also it misses the initialization of this field in the buffer, this may lead to a situation where we stop the sw retransmission of failed subframes associated to this buffer. Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-26compat-wireless: remove two pending patches now upstreamLuis R. Rodriguez
These patches are now upstream: commit a65e4cb402b5f3e120570ba1faca4354d47e8f2f Author: Felix Fietkau <nbd@openwrt.org> Date: Thu May 13 20:37:25 2010 +0200 ath9k: remove VEOL support for ad-hoc With VEOL, Beacon transmission in ad-hoc does not currently work. I believe for larger ad-hoc networks, VEOL is too unreliable, as it can get beacon transmissions stuck during synchronization. Use SWBA based beacon trasmission similar to AP mode instead. Signed-off-by: Felix Fietkau <nbd@openwrt.org> Acked-by: Benoit Papillault <benoit.papillault@free.fr> Signed-off-by: John W. Linville <linville@tuxdriver.com> commit 774610e4f26cb3d9da14a8b5974324c9e51017bd Author: Felix Fietkau <nbd@openwrt.org> Date: Thu May 13 20:37:24 2010 +0200 ath9k: change beacon allocation to prefer the first beacon slot This fixes IBSS beacon transmissions without VEOL enabled Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com> This reduces the pending stuff: 7132 - Code changes posted but not yet merged 4449 - Code additions posted but not yet merged 2683 - Code deletions posted but not yet merged 1.45 - % of code not yet merged Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-25compat-wireless: add new set of pending patches for 2010-05-25Luis R. Rodriguez
This just adds three patches by Felix posted today. To generate these and merge these back into this tree though I am using a very crude technique though: I cherry pick patches from the mailing lists, I then git am them onto a local wireless-testing tree, then I git format-patch -o compat-pending-05-25 origin..pending-sha1sum Then I git rm linux-next-pending/*.patch and add the new series. This is a bit sloppy, I admit it but it works well for how I am managing it. If you need a patch sucked into this series let me know and I'll go ahead and merge it as well. For now I am just taking in things I see as important for ath9k, mac80211 and cfg80211. If you want to consider your drivers just ask in the linux-wireless / linux-bluetooth list (cc'ing me or something) annotating the patch for me to be picked up. At least lets try it for now this way and see it how it goes. If you think of something better let me know. These pending patches are applied with the -p option of ./scripts/admin-update.sh -p Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-25compat-wireless: ./scripts/admin-update.sh -p refreshLuis R. Rodriguez
Runs reresh on the pending patches. There are no automatic tarballs using this yet. 6809 - Code changes posted but not yet merged 4398 - Code additions posted but not yet merged 2411 - Code deletions posted but not yet merged 1.39 - % of code not yet merged Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-25compat-wireless: remove pending patches as of next-20100525Luis R. Rodriguez
This only affects tarballs created with the ./scripts/admin-update.sh -p option Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-21compat-wireless: add a set of pending patches for linux-wirelessLuis R. Rodriguez
We're in the merge window, so this adds all the patches pending merge from Atheros. Note that these are not applied by default, to apply then you must use the "-p" flag for ./scripts/admin-update.sh Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
2010-05-21compat-wireless: add linux-next-pending, crap patch dirs and nagometerLuis R. Rodriguez
Sometimes you have no other option but to carry around patches. This can happen for a variety of reasons. Ultimately testing of code cannot happen on the kernel maintainer's clock but on your own. This expands the idea of the linux-next-cherry-pick patch directory on compat-wireless to also allow for patches to be merged which are posted to some mailing list but pending merge due to some reasons (merge window is a good example). It also adds a crap patch directory for those really nasty situations you can run into where you have no other option but to give someone a release with some delta even if the patch is not yet posted anywhere. The focus should always be upstream though so to avoid these situations we will also provide code metrics to indicate to the package maintainer how much code came from each directory, including the backport code to support older kernel releases. Maybe we should add the code-metrics.txt file as a print out on the compat module load :) Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>