From: Jiri Slaby <jslaby@suse.cz>
To: "Greg KH" <gregkh@linuxfoundation.org>,
"Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: stable@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Please backport shrink dentry list fixes to stable
Date: Wed, 19 Nov 2014 22:12:50 +0100 [thread overview]
Message-ID: <546D07D2.2040605@suse.cz> (raw)
In-Reply-To: <20141119204205.GA20905@kroah.com>
On 11/19/2014, 09:42 PM, Greg KH wrote:
> It looks like Cong provided a better documented / tested series for this
> as well, so that will make it easier to accept for a future kernel than
> this assorted list of git commit ids...
On the top of that I only wanted to add here, that it has some testing
coverage from the SLE12 tree too. We were dragging the series in there
for some time until I finally pushed them into 3.12.32.
thanks,
--
js
suse labs
prev parent reply other threads:[~2014-11-19 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 20:50 Please backport shrink dentry list fixes to stable Cong Wang
2014-10-03 20:24 ` Holger Hoffstätte
2014-11-19 17:39 ` Greg KH
2014-11-19 18:44 ` Holger Hoffstätte
2014-11-19 20:38 ` Greg KH
2014-11-19 20:42 ` Greg KH
2014-11-19 21:12 ` Jiri Slaby [this message]
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=546D07D2.2040605@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.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).