From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1759163AbbA3BgA (ORCPT <rfc822;w@1wt.eu>);
	Thu, 29 Jan 2015 20:36:00 -0500
Received: from mail-ie0-f173.google.com ([209.85.223.173]:56376 "EHLO
	mail-ie0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1757281AbbA3Bf7 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 29 Jan 2015 20:35:59 -0500
MIME-Version: 1.0
In-Reply-To: <CA+55aFxYo1fpVoGVXhA0VPNAKKEZPAQDpF47pk+yPSnArvDEdA@mail.gmail.com>
References: <CA+55aFxNk9OCXz7nvKXpRBc0Z85NLXPNkRm1yJf4-KAGB4pHRA@mail.gmail.com>
	<1421878320.4903.17.camel@stgolabs.net>
	<54C02E08.4080405@hurleysoftware.com>
	<1861286.x5DC37NGWz@vostro.rjw.lan>
	<CA+55aFzWGCO16v3NL7SqgBnQQrwpwCTvFZR=+3x89Hg0KzJtxg@mail.gmail.com>
	<CA+55aFxYo1fpVoGVXhA0VPNAKKEZPAQDpF47pk+yPSnArvDEdA@mail.gmail.com>
Date: Thu, 29 Jan 2015 17:35:58 -0800
X-Google-Sender-Auth: xoqSSatqOEB4EjhHoBX2TT6FsKs
Message-ID: <CA+55aFyTWE+ZJEUvGXXomzoh1XNY5cei2HoNDfuJKyH6zE_zYg@mail.gmail.com>
Subject: Re: Linux 3.19-rc5
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Ingo Molnar <mingo@kernel.org>
Cc: Peter Hurley <peter@hurleysoftware.com>,
        Davidlohr Bueso <dave@stgolabs.net>,
        Peter Zijlstra <peterz@infradead.org>,
        =?UTF-8?Q?Bruno_Pr=C3=A9mont?= <bonbons@linux-vserver.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ilya Dryomov <ilya.dryomov@inktank.com>,
        Mike Galbraith <umgwanakikbuti@gmail.com>,
        Oleg Nesterov <oleg@redhat.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 29, 2015 at 5:25 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Ingo, maybe you'd want to apply this through the scheduler tree, the
> way you already did the WARN_ONCE() thing.

Side note: I can obviously just commit it myself, but for things that
have obvious maintainers I tend to try to try to push the changes
through channels.

                            Linus