From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
stable@vger.kernel.org
Subject: [ 0/7] 3.0.95-stable review
Date: Thu, 5 Sep 2013 13:28:33 -0700 [thread overview]
Message-ID: <20130905202757.642048278@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 3.0.95 release.
There are 7 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 Sat Sep 7 20:27:46 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.95-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 3.0.95-rc1
Roland Dreier <roland@purestorage.com>
SCSI: sg: Fix user memory corruption when SG_IO is interrupted by a signal
Nicholas Bellinger <nab@linux-iscsi.org>
target: Fix trailing ASCII space usage in INQUIRY vendor+model
Lan Tianyu <tianyu.lan@intel.com>
ACPI / EC: Add ASUSTEK L4R to quirk list in order to validate ECDT
Helmut Schaa <helmut.schaa@googlemail.com>
ath9k_htc: Restore skb headroom when returning skb to mac80211
Russ Anderson <rja@sgi.com>
drivers/base/memory.c: fix show_mem_removable() to handle missing sections
Takashi Iwai <tiwai@suse.de>
ALSA: opti9xx: Fix conflicting driver object name
Dave Kleikamp <dave.kleikamp@oracle.com>
jfs: fix readdir cookie incompatibility with NFSv4
-------------
Diffstat:
Makefile | 4 ++--
drivers/acpi/ec.c | 4 ++++
drivers/base/memory.c | 2 ++
drivers/net/wireless/ath/ath9k/htc_drv_txrx.c | 10 +++++++++
drivers/target/target_core_cdb.c | 11 +++++-----
fs/bio.c | 20 ++++++++++++-----
fs/jfs/jfs_dtree.c | 31 ++++++++++++++++++++-------
sound/isa/opti9xx/opti92x-ad1848.c | 8 ++-----
8 files changed, 64 insertions(+), 26 deletions(-)
next reply other threads:[~2013-09-05 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:28 Greg Kroah-Hartman [this message]
2013-09-05 20:28 ` [ 1/7] jfs: fix readdir cookie incompatibility with NFSv4 Greg Kroah-Hartman
2013-09-05 20:28 ` [ 2/7] ALSA: opti9xx: Fix conflicting driver object name Greg Kroah-Hartman
2013-09-05 20:28 ` [ 3/7] drivers/base/memory.c: fix show_mem_removable() to handle missing sections Greg Kroah-Hartman
2013-09-05 20:28 ` [ 4/7] ath9k_htc: Restore skb headroom when returning skb to mac80211 Greg Kroah-Hartman
2013-09-05 20:28 ` [ 5/7] ACPI / EC: Add ASUSTEK L4R to quirk list in order to validate ECDT Greg Kroah-Hartman
2013-09-05 20:28 ` [ 6/7] target: Fix trailing ASCII space usage in INQUIRY vendor+model Greg Kroah-Hartman
2013-09-05 20:28 ` [ 7/7] SCSI: sg: Fix user memory corruption when SG_IO is interrupted by a signal Greg Kroah-Hartman
2013-09-05 22:54 ` [ 0/7] 3.0.95-stable review Guenter Roeck
2013-09-06 16:39 ` Greg Kroah-Hartman
2013-09-06 17:52 ` Shuah Khan
2013-09-06 18:46 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130905202757.642048278@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).