From: Paul Bolle <pebolle@tiscali.nl>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.4 0/2] 4.4.26-stable review
Date: Wed, 19 Oct 2016 20:52:55 +0200 [thread overview]
Message-ID: <1476903175.28989.4.camel@tiscali.nl> (raw)
In-Reply-To: <20161019182806.226441558@linuxfoundation.org>
On Wed, 2016-10-19 at 20:30 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.26 release.
> There are 2 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.
Did I botch my attempt at a backport of "lightnvm: ensure that
nvm_dev_ops can be used without CONFIG_NVM" to v4.4.y (see
https://lkml.kernel.org/r/<1476477349-28155-1-git-send-email-pebolle@ti
scali.nl> ) sufficiently for it to be dropped?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2016-10-19 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161019183058uscas1p2a99684ab1f1ff2ddce42c2d37ad90107@uscas1p2.samsung.com>
2016-10-19 18:30 ` [PATCH 4.4 0/2] 4.4.26-stable review Greg Kroah-Hartman
2016-10-19 18:30 ` [PATCH 4.4 1/2] x86/build: Build compressed x86 kernels as PIE Greg Kroah-Hartman
2016-10-19 18:30 ` [PATCH 4.4 2/2] mm: remove gup_flags FOLL_WRITE games from __get_user_pages() Greg Kroah-Hartman
2016-10-19 18:52 ` Paul Bolle [this message]
2016-10-19 19:34 ` [PATCH 4.4 0/2] 4.4.26-stable review Greg Kroah-Hartman
2016-10-19 19:41 ` Paul Bolle
2016-10-19 22:28 ` Shuah Khan
2016-10-20 1:41 ` Guenter Roeck
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=1476903175.28989.4.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--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).