stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	linux@roeck-us.net, shuah.kh@samsung.com, patches@kernelci.org,
	ben.hutchings@codethink.co.uk, stable@vger.kernel.org
Subject: [PATCH 4.8 0/4] 4.8.3-stable review
Date: Wed, 19 Oct 2016 20:31:25 +0200	[thread overview]
Message-ID: <20161019182927.746970025@linuxfoundation.org> (raw)

This is the start of the stable review cycle for the 4.8.3 release.
There are 4 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 Fri Oct 21 18:29:21 UTC 2016.
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/v4.x/stable-review/patch-4.8.3-rc1.gz
or in the git tree and branch at:
  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.8.y
and the diffstat can be found below.

thanks,

greg k-h

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

Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Linux 4.8.3-rc1

Linus Torvalds <torvalds@linux-foundation.org>
    mm: remove gup_flags FOLL_WRITE games from __get_user_pages()

Artem Savkov <asavkov@redhat.com>
    Make __xfs_xattr_put_listen preperly report errors.

Heiner Kallweit <hkallweit1@gmail.com>
    scsi: configure runtime pm before calling device_add in scsi_add_host_with_dma

Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
    v4l: rcar-fcp: Don't force users to check for disabled FCP support


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

Diffstat:

 Makefile                 |  4 ++--
 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, 25 insertions(+), 9 deletions(-)



             reply	other threads:[~2016-10-19 18:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161019183131uscas1p2a3227010e6cca676e3d69310f26c86d4@uscas1p2.samsung.com>
2016-10-19 18:31 ` Greg Kroah-Hartman [this message]
2016-10-19 18:31   ` [PATCH 4.8 1/4] [media] v4l: rcar-fcp: Dont force users to check for disabled FCP support Greg Kroah-Hartman
2016-10-19 18:31   ` [PATCH 4.8 2/4] scsi: configure runtime pm before calling device_add in scsi_add_host_with_dma Greg Kroah-Hartman
2016-10-19 18:31   ` [PATCH 4.8 3/4] Make __xfs_xattr_put_listen preperly report errors Greg Kroah-Hartman
2016-10-19 18:31   ` [PATCH 4.8 4/4] mm: remove gup_flags FOLL_WRITE games from __get_user_pages() Greg Kroah-Hartman
2016-10-19 22:30   ` [PATCH 4.8 0/4] 4.8.3-stable review Shuah Khan
2016-10-20  8:14     ` Greg Kroah-Hartman
2016-10-20  1:44   ` Guenter Roeck
2016-10-20  8:15     ` 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=20161019182927.746970025@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=patches@kernelci.org \
    --cc=shuah.kh@samsung.com \
    --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).