path: root/patches/collateral-evolutions/network
AgeCommit message (Collapse)Author
2012-12-18compat-drivers: refresh patches for next-20121218Luis R. Rodriguez
Signed-off-by: Luis R. Rodriguez <>
2012-12-14compat-drivers: refresh patches for next-20121214Luis R. Rodriguez
Signed-off-by: Luis R. Rodriguez <>
2012-12-12compat-drivers: refresh patches for next-20121211Luis R. Rodriguez
Signed-off-by: Luis R. Rodriguez <>
2012-12-11compat-drivers: remove 67-use_spinlock_t.patchLuis R. Rodriguez
This work is now upstream. Signed-off-by: Luis R. Rodriguez <>
2012-12-11compat-drivers: fix 62-usb_driver_lpm.patchLuis R. Rodriguez
CONFIG_HOTPLUG is going away soon so a few helpers can be removed now. Signed-off-by: Luis R. Rodriguez <>
2012-12-11compat-drivers: fix 45-remove-platform-id-table.patchLuis R. Rodriguez
CONFIG_HOTPLUG is going away soon so a few init/remove helpers are being removed. Signed-off-by: Luis R. Rodriguez <>
2012-12-11compat-drivers: remove __devexit_p() from 11-dev-pm-ops.patchLuis R. Rodriguez
The __devexit_p() was removed from a few drivers given that CONFIG_HOTPLUG is going away. Signed-off-by: Luis R. Rodriguez <>
2012-12-11compat-drivers: remove ksize() ifdef on scan.cLuis R. Rodriguez
The patch bellow remove the usage of ksize() so just remove that hunk. commit 9caf03640279e64d0ba36539b42daa1b43a49486 Author: Johannes Berg <> Date: Thu Nov 29 01:25:20 2012 +0100 cfg80211: fix BSS struct IE access races When a BSS struct is updated, the IEs are currently overwritten or freed. This can lead to races if some other CPU is accessing the BSS struct and using the IEs concurrently. Fix this by always allocating the IEs in a new struct that holds the data and length and protecting access to this new struct with RCU. Signed-off-by: Johannes Berg <> Signed-off-by: Luis R. Rodriguez <>
2012-12-03compat-drivers: fix 11-dev-pm-ops.patchLuis R. Rodriguez
Hauke had sent out patches to help clean up the pm run time callbacks to allow this patch to be simplified. This takes care of the required changes. This goes compile tested against next-20121203 mcgrof@drvbp1 ~/devel/compat-drivers (git::master)$ time ckmake Trying kernel 3.6.5-030605-generic [OK] Trying kernel 3.5.7-030507-generic [OK] Trying kernel 3.4.17-030417-generic [OK] Trying kernel 3.3.8-030308-generic [OK] Trying kernel 3.2.33-030233-generic [OK] Trying kernel 3.1.10-030110-generic [OK] Trying kernel 3.0.50-030050-generic [OK] Trying kernel 2.6.39-02063904-generic [OK] Trying kernel 2.6.38-02063808-generic [OK] Trying kernel 2.6.37-02063706-generic [OK] Trying kernel 2.6.36-02063604-generic [OK] Trying kernel 2.6.35-02063513-generic [OK] Trying kernel 2.6.34-02063413-generic [OK] Trying kernel 2.6.33-02063320-generic [OK] Trying kernel 2.6.32-02063260-generic [OK] Trying kernel 2.6.31-02063113-generic [OK] Trying kernel 2.6.30-02063010-generic [OK] Trying kernel 2.6.29-02062906-generic [OK] Trying kernel 2.6.28-02062810-generic [OK] Trying kernel 2.6.27-020627-generic [OK] Trying kernel 2.6.26-020626-generic [OK] Trying kernel 2.6.25-020625-generic [OK] Trying kernel 2.6.24-020624-generic [OK] real 18m42.239s user 327m50.029s sys 53m37.317s Signed-off-by: Luis R. Rodriguez <>
2012-11-29compat-drivers: move all patch types under patches/Luis R. Rodriguez
The number of patch directories for the different life cycle a patch can be on its way upstream had reached 4: * pending-stable * linux-next-pending * linux-next-cherry-picks * crap Apart from this we also had the backport related patches. In the future I see potential for other directories for different categories of patches. Consider how we are breaking down the backport patches into specific documented collateral evolutions and of those type of collateral evolutions there may be different types of collateral evolutions which we could likely treat / document differently. Another type of patch that I forsee us having to deal with are patches for drivers that are not upstrea -- like crap, but for drivers in a unified driver tree that is *designed* from scratch to be targetting upstream Linux inclusion using the same coccinelle technology I forsee us using for backporting collateral evolutions. Since the number of patch directories can get out of hand at the top level lets just stuff then all under patches/ and deal with patches there. This also places the backport patches into a directory called collateral-evolutions/ to help promote and educate on the nature of the changes that we have to deal with when backporting. Cc: Julia Lawall <> Cc: Adrian Chadd <> Signed-off-by: Luis R. Rodriguez <>