From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Linux 3.4.23
Date: Mon, 10 Dec 2012 11:47:05 -0800 [thread overview]
Message-ID: <20121210194705.GA19757@kroah.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3407 bytes --]
I'm announcing the release of the 3.4.23 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
thanks,
greg k-h
------------
Makefile | 2
arch/arm/Kconfig | 1
arch/arm/mach-dove/include/mach/pm.h | 2
arch/arm/mach-dove/irq.c | 14 +
arch/arm/mach-kirkwood/pcie.c | 11 -
arch/x86/include/asm/fpu-internal.h | 15 +
arch/x86/kernel/smpboot.c | 5
drivers/acpi/processor_driver.c | 1
drivers/edac/i7300_edac.c | 8
drivers/gpu/drm/i915/intel_lvds.c | 16 +
drivers/gpu/drm/radeon/evergreen.c | 191 +++++++++++------------
drivers/gpu/drm/radeon/evergreen_reg.h | 2
drivers/gpu/drm/radeon/evergreend.h | 7
drivers/gpu/drm/radeon/radeon_asic.h | 1
drivers/md/raid10.c | 100 ++++++------
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 11 -
fs/nfs/blocklayout/blocklayout.c | 176 +++++++++++++++++++--
fs/nfs/blocklayout/blocklayout.h | 1
kernel/sched/auto_group.c | 4
kernel/sched/auto_group.h | 5
kernel/workqueue.c | 4
mm/memory-failure.c | 8
mm/sparse.c | 10 -
scripts/package/buildtar | 2
24 files changed, 406 insertions(+), 191 deletions(-)
Alan Cox (1):
ACPI: missing break
Alex Deucher (3):
drm/radeon/dce4+: don't use radeon_crtc for vblank callback
drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2)
drm/radeon: properly track the crtc not_enabled case evergreen_mc_stop()
Ariel Elior (1):
bnx2x: remove redundant warning log
Calvin Walton (1):
i915: Quirk no_lvds on Gigabyte GA-D525TUD ITX motherboard
Chris Wilson (1):
drm/i915: Add no-lvds quirk for Supermicro X7SPA-H
Greg Kroah-Hartman (1):
Linux 3.4.23
Jason Gunthorpe (1):
ARM: Kirkwood: Update PCI-E fixup
Jean Delvare (1):
i7300_edac: Fix error flag testing
Jianguo Wu (1):
mm/vmemmap: fix wrong use of virt_to_page
Michal Marek (1):
kbuild: Do not package /boot and /lib in make tar-pkg
Mike Galbraith (2):
workqueue: exit rescuer_thread() as TASK_RUNNING
Revert "sched, autogroup: Stop going ahead if autogroup is disabled"
Naoya Horiguchi (1):
mm: soft offline: split thp at the beginning of soft_offline_page()
NeilBrown (1):
md/raid10: close race that lose writes lost when replacement completes.
Peng Tao (1):
pnfsblock: fix partial page buffer wirte
Russell King - ARM Linux (2):
Dove: Attempt to fix PMU/RTC interrupts
Dove: Fix irq_to_pmu()
Vincent Palatin (1):
x86, fpu: Avoid FPU lazy restore after suspend
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-12-10 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 19:47 Greg KH [this message]
2012-12-10 19:47 ` Greg KH
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=20121210194705.GA19757@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--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
all inboxes | Powered by JetHome®