This is the start of the stable review cycle for the 3.0.25 release.
There are 38 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Mar 18 23:00:00 UTC 2012.
Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.0.25-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Makefile | 4 +-
arch/s390/kernel/setup.c | 1 +
arch/sparc/Makefile | 2 +-
arch/x86/lib/delay.c | 4 +-
block/genhd.c | 42 +++++-----
drivers/base/core.c | 6 +-
drivers/block/sx8.c | 2 +-
drivers/firewire/core-cdev.c | 24 +++++-
drivers/firewire/core-device.c | 15 ++--
drivers/hwmon/w83627ehf.c | 9 +--
drivers/i2c/algos/i2c-algo-bit.c | 8 +-
drivers/net/atl1c/atl1c_main.c | 4 -
drivers/net/ppp_generic.c | 23 ++++++
drivers/net/sfc/rx.c | 4 +-
drivers/net/usb/asix.c | 4 +
drivers/net/vmxnet3/vmxnet3_drv.c | 7 +-
drivers/net/vmxnet3/vmxnet3_int.h | 4 +-
drivers/net/wireless/rt2x00/rt2x00dev.c | 6 +-
drivers/net/wireless/rt2x00/rt2x00mac.c | 9 +++
drivers/net/wireless/rt2x00/rt2x00queue.c | 3 +
drivers/pci/pcie/aspm.c | 3 +
drivers/platform/x86/acer-wmi.c | 121 ++++++++++++++++++++++++-----
drivers/regulator/tps6524x-regulator.c | 2 +-
drivers/s390/char/fs3270.c | 1 +
fs/aio.c | 22 +++---
fs/block_dev.c | 16 +++-
fs/namei.c | 4 +-
fs/partitions/check.c | 48 ++++++++++--
include/linux/genhd.h | 1 +
include/linux/skbuff.h | 10 +++
include/linux/workqueue.h | 4 +
kernel/workqueue.c | 7 +-
net/bridge/br_multicast.c | 7 +-
net/core/neighbour.c | 2 +
net/ipv4/tcp_input.c | 23 ++++--
net/ipv4/xfrm4_mode_beet.c | 5 +-
net/ipv4/xfrm4_mode_tunnel.c | 6 +-
net/ipv6/addrconf.c | 4 +
net/ipv6/xfrm6_mode_beet.c | 6 +-
net/ipv6/xfrm6_mode_tunnel.c | 6 +-
sound/soc/samsung/neo1973_wm8753.c | 4 +-
41 files changed, 351 insertions(+), 132 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
