All of lore.kernel.org
 help / color / mirror / Atom feed
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 4.8.3
Date: Thu, 20 Oct 2016 11:12:12 +0200	[thread overview]
Message-ID: <20161020091212.GB7991@kroah.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

I'm announcing the release of the 4.8.3 kernel.

All users of the 4.8 kernel series must upgrade.

The updated 4.8.y git tree can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.8.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 +-
 drivers/scsi/hosts.c     |   12 ++++++++----
 fs/xfs/xfs_xattr.c       |    1 +
 include/linux/mm.h       |    1 +
 include/media/rcar-fcp.h |    2 +-
 mm/gup.c                 |   14 ++++++++++++--
 6 files changed, 24 insertions(+), 8 deletions(-)

Artem Savkov (1):
      Make __xfs_xattr_put_listen preperly report errors.

Greg Kroah-Hartman (1):
      Linux 4.8.3

Heiner Kallweit (1):
      scsi: configure runtime pm before calling device_add in scsi_add_host_with_dma

Laurent Pinchart (1):
      v4l: rcar-fcp: Don't force users to check for disabled FCP support

Linus Torvalds (1):
      mm: remove gup_flags FOLL_WRITE games from __get_user_pages()


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2016-10-20  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20  9:12 Greg KH [this message]
2016-10-20  9:12 ` Linux 4.8.3 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=20161020091212.GB7991@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.