This is the start of the stable review cycle for the 3.0.85 release.
There are 8 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 Wed Jul  3 19:59:07 UTC 2013.
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.85-rc1.gz
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <gre...@linuxfoundation.org>
    Linux 3.0.85-rc1

Liang Li <liang...@windriver.com>
    pch_uart: fix a deadlock when pch_uart as console

Artem Bityutskiy <artem.bityuts...@linux.intel.com>
    UBIFS: fix a horrid bug

Artem Bityutskiy <artem.bityuts...@linux.intel.com>
    UBIFS: prepare to fix a horrid bug

Stephane Eranian <eran...@google.com>
    perf: Disable monitoring on setuid processes for regular users

Zefan Li <lize...@huawei.com>
    dlci: validate the net device in dlci_del()

Zefan Li <lize...@huawei.com>
    dlci: acquire rtnl_lock before calling __dev_get_by_name()

Oleg Nesterov <o...@redhat.com>
    hw_breakpoint: Use cpu_possible_mask in {reserve,release}_bp_slot()

Anderson Lizardo <anderson.liza...@openbossa.org>
    Bluetooth: Fix crash in l2cap_build_cmd() with small MTU


-------------

Diffstat:

 Makefile                      |  4 ++--
 drivers/net/wan/dlci.c        | 26 +++++++++++++++++----
 drivers/tty/serial/pch_uart.c | 29 +++++++++++++++++------
 fs/exec.c                     | 16 +++++++------
 fs/ubifs/dir.c                | 54 +++++++++++++++++++++++++++++++------------
 kernel/events/hw_breakpoint.c |  4 ++--
 net/bluetooth/l2cap_core.c    |  3 +++
 7 files changed, 98 insertions(+), 38 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to