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 S1755360AbdDNWjK (ORCPT <rfc822;w@1wt.eu>);
        Fri, 14 Apr 2017 18:39:10 -0400
Received: from cloudserver094114.home.net.pl ([79.96.170.134]:63418 "EHLO
        cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1751462AbdDNWjH (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 14 Apr 2017 18:39:07 -0400
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Michal Hocko <mhocko@kernel.org>, Joey Lee <jlee@suse.com>,
        Jiri Kosina <jkosina@suse.cz>, Kani Toshimitsu <toshi.kani@hpe.com>,
        Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
        ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
        linux-api@vger.kernel.org
Subject: Re: [PATCH] acpi: drop support for force_remove
Date: Sat, 15 Apr 2017 00:33:06 +0200
Message-ID: <13091724.qdDQ4T8Luo@aspire.rjw.lan>
User-Agent: KMail/4.14.10 (Linux/4.11.0-rc6+; KDE/4.14.9; x86_64; ; )
In-Reply-To: <CAJZ5v0hzv1oxpNJvSc2omqaOFRgiBB8UKCbRKGkgzHbEtqosbQ@mail.gmail.com>
References: <20170403074023.29121-1-mhocko@kernel.org> <20170411135233.GO6729@dhcp22.suse.cz> <CAJZ5v0hzv1oxpNJvSc2omqaOFRgiBB8UKCbRKGkgzHbEtqosbQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tuesday, April 11, 2017 03:54:43 PM Rafael J. Wysocki wrote:
> On Tue, Apr 11, 2017 at 3:52 PM, Michal Hocko <mhocko@kernel.org> wrote:
> > On Tue 11-04-17 15:48:04, Rafael J. Wysocki wrote:
> >> On Tue, Apr 11, 2017 at 2:20 PM, Michal Hocko <mhocko@kernel.org> wrote:
> >> > On Tue 11-04-17 00:15:42, Rafael J. Wysocki wrote:
> > [...]
> >> >> I'll apply it if nobody has any problems with it.
> >> >
> >> > It is definitely your call but how long are we going to wait
> >> > (considering that the current behavior is obviously broken wrt memory
> >> > hotplug)?
> >>
> >> A couple of days more?  Surely not going to push it into 4.11 at this
> >> stage as it is an ABI change.
> >
> > Ohh, I didn't want to push it to 4.11 this late but having it in
> > linux-next might help to catch some users who are not following the
> > mailing list. Going to 4.12 would be really great but I wouldn't really
> > object even 4.13...
> 
> 4.12 is probably fine.  I don't see a compelling reason to sit on this
> for a whole cycle, FWIW.

It should hit linux-next next week.

Thanks,
Rafael