| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
SVN-Revision: 27527
|
|
|
|
| |
SVN-Revision: 27524
|
|
|
|
| |
SVN-Revision: 27518
|
|
|
|
| |
SVN-Revision: 27514
|
|
|
|
| |
SVN-Revision: 27492
|
|
|
|
| |
SVN-Revision: 27491
|
|
|
|
| |
SVN-Revision: 27490
|
|
|
|
|
|
| |
not-yet-upstreamed stuff
SVN-Revision: 27485
|
|
|
|
| |
SVN-Revision: 27483
|
|
|
|
| |
SVN-Revision: 27464
|
|
|
|
| |
SVN-Revision: 27457
|
|
|
|
| |
SVN-Revision: 27454
|
|
|
|
| |
SVN-Revision: 27390
|
|
|
|
|
|
|
|
| |
couple of weeks.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27373
|
|
|
|
|
|
|
|
| |
require the MFD driver to be present for the BAR's to be mapped.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27371
|
|
|
|
|
|
|
|
| |
MFD driver to be present for the BAR's to be mapped."
This reverts commit c485487b63d1c1de72a375f1278d8a98546ba3af.
SVN-Revision: 27370
|
|
|
|
|
|
|
|
| |
driver to be present for the BAR's to be mapped.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27369
|
|
|
|
| |
SVN-Revision: 27327
|
|
|
|
|
|
| |
unlocked_ioctl on all platforms and fix the arguments to the ioctl handler (based on patch from #9198)
SVN-Revision: 27322
|
|
|
|
| |
SVN-Revision: 27305
|
|
|
|
| |
SVN-Revision: 27300
|
|
|
|
| |
SVN-Revision: 27299
|
|
|
|
| |
SVN-Revision: 27295
|
|
|
|
| |
SVN-Revision: 27293
|
|
|
|
| |
SVN-Revision: 27269
|
|
|
|
| |
SVN-Revision: 27247
|
|
|
|
|
|
|
|
|
|
|
|
| |
bridge module has a dependency to IPv6 if IPv6 is enabled. Since the IPv6 module isn't exactly lightweight and bridge also only needs a single function from IPv6, it's rather easy to create a common "lib" module with a RCU pointer to the actual implementation, if the IPv6 module is loaded (although slightly hackish).
The codepath seems to be only taken when using IPv6, so there should be
no negative side effects when IPv6 isn't loaded. I did not measure how
big the performance impact is.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 27237
|
|
|
|
| |
SVN-Revision: 27218
|
|
|
|
| |
SVN-Revision: 27195
|
|
|
|
|
|
|
|
| |
Also make linux identify itself properly as 3.0, not 3.0.0.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 27191
|
|
|
|
|
|
|
|
| |
defined.
Signed-off-by: Philip A. Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27182
|
|
|
|
| |
SVN-Revision: 27181
|
|
|
|
|
|
| |
(netfilter: IPv6: fix DSCP mangle code)
SVN-Revision: 27179
|
|
|
|
| |
SVN-Revision: 27178
|
|
|
|
| |
SVN-Revision: 27143
|
|
|
|
| |
SVN-Revision: 27111
|
|
|
|
| |
SVN-Revision: 27105
|
|
|
|
|
|
| |
patch from Peter Wagner
SVN-Revision: 27104
|
|
|
|
| |
SVN-Revision: 27074
|
|
|
|
| |
SVN-Revision: 27073
|
|
|
|
|
|
|
|
|
| |
* remove lqtapi
* bump tapi/dsl to .39
* migrate to new ltq_ style api
* add amazon_se support
SVN-Revision: 27026
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was originally tristate, but was changed to bool to prevent a build
breakage in an earlier patch revision (for a new syscall). The actual
commit[1] changed it in a way this isn't needed anymore, but
accidentially left the EXPORTFS change in. There's no reason for it
not being buildable as a module, so changing it back to tristate is
fine.
see: https://patchwork.kernel.org/patch/812832/
Thank you Jonas Gorski for the patch.
SVN-Revision: 27011
|
|
|
|
|
|
|
|
|
|
|
| |
* Add missing config symbols
* Update package/kernel for 2.6.39
CONFIG_BT_L2CAP=y and CONFIG_BT_SCO=y are set to build them into the bluetooth module.
Thank you Jonas Gorski for the patch
SVN-Revision: 27010
|
|
|
|
|
|
|
|
|
|
| |
* add md5sum for kernel
* add some missing config symbols
* add some ssb patches to make compat-wireless compile
Thank you Peter Wagner for the patch
SVN-Revision: 27009
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes for the following warnings:
drivers/mtd/devices/block2mtd.c: In function '_open_bdev':
drivers/mtd/devices/block2mtd.c:272:3: warning: ISO C90 forbids mixed declarations and code
drivers/mtd/devices/block2mtd.c: In function 'add_device':
drivers/mtd/devices/block2mtd.c:399:13: warning: assignment discards qualifiers from pointer target type
In the case of 442-block2mtd_probe.patch, it's not until the insertion of a executable statement before the definition that causes a warning, so I've chosen to resolve the issue here by splitting the definition and the initialization into a definition and a statement (and assignment) instead.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27007
|
|
|
|
| |
SVN-Revision: 26997
|
|
|
|
| |
SVN-Revision: 26955
|
|
|
|
| |
SVN-Revision: 26911
|
|
|
|
| |
SVN-Revision: 26908
|
|
|
|
| |
SVN-Revision: 26906
|