[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hzv1oxpNJvSc2omqaOFRgiBB8UKCbRKGkgzHbEtqosbQ@mail.gmail.com>
Date: Tue, 11 Apr 2017 15:54:43 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Michal Hocko <mhocko@...nel.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, Joey Lee <jlee@...e.com>,
Jiri Kosina <jkosina@...e.cz>,
Kani Toshimitsu <toshi.kani@....com>,
Len Brown <lenb@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
linux-api@...r.kernel.org
Subject: Re: [PATCH] acpi: drop support for force_remove
On Tue, Apr 11, 2017 at 3:52 PM, Michal Hocko <mhocko@...nel.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@...nel.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.
Thanks,
Rafael
Powered by blists - more mailing lists