From: Jiri Slaby <jslaby@suse.cz>
To: Josh Boyer <jwboyer@fedoraproject.org>, Greg KH <greg@kroah.com>,
mhocko@suse.cz
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Kernel Fedora <kernel@lists.fedoraproject.org>
Subject: Re: Feb. Fedora Kernel Patch Report
Date: Wed, 26 Mar 2014 15:51:35 +0100 [thread overview]
Message-ID: <5332E977.8010102@suse.cz> (raw)
In-Reply-To: <CA+5PVA608SPM1r5tXwo_C+vaEff+XiLQ5AWwH7-i-MMGcXtuHw@mail.gmail.com>
On 03/26/2014 02:44 PM, Josh Boyer wrote:
> On Tue, Mar 25, 2014 at 5:24 PM, Greg KH <greg@kroah.com> wrote:
>> On Fri, Feb 28, 2014 at 10:13:29AM -0500, Josh Boyer wrote:
>>> cgroup-fixes.patch (rhbz 1045755)
>>> - Upstream commits 0ab02ca8f887908152d1a96db5130fc661d36a1e
>>> - There was a 3.12 version of this patch sent to stable list from
>>> Michal Hocko. I don't remember why it wasn't applied, or why it
>>> wasn't applied for 3.13.y...
>>
>> It didn't apply to 3.13, and I think I was waiting for a backported
>> version, do you have one?
>
> As far as I know we're using this version:
>
> http://thread.gmane.org/gmane.linux.kernel.cgroups/10336/focus=1646465
>
> The commentary on the thread seems to imply that Michal was going to
> send it again for some reason. Michal, did you send the 3.12/3.13
> backport for this commit directly to stable?
In the meantime, I applied to the stable 3.12 Michal's version from suse
enterprise 12. I believe that it is the same as in the link above.
Please confirm.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2014-03-26 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 15:13 Feb. Fedora Kernel Patch Report Josh Boyer
2014-03-03 12:22 ` Luís Henriques
2014-03-03 12:22 ` Luís Henriques
2014-03-25 21:24 ` Greg KH
2014-03-26 13:44 ` Josh Boyer
2014-03-26 14:51 ` Jiri Slaby [this message]
2014-03-26 21:16 ` Michal Hocko
2014-03-31 23:58 ` 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=5332E977.8010102@suse.cz \
--to=jslaby@suse.cz \
--cc=greg@kroah.com \
--cc=jwboyer@fedoraproject.org \
--cc=kernel@lists.fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--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 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.