linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>, 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: Tue, 11 Apr 2017 15:54:43 +0200	[thread overview]
Message-ID: <CAJZ5v0hzv1oxpNJvSc2omqaOFRgiBB8UKCbRKGkgzHbEtqosbQ@mail.gmail.com> (raw)
In-Reply-To: <20170411135233.GO6729@dhcp22.suse.cz>

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.

Thanks,
Rafael

  reply	other threads:[~2017-04-11 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  7:40 [PATCH] acpi: drop support for force_remove Michal Hocko
2017-04-10 17:13 ` Michal Hocko
2017-04-10 22:15   ` Rafael J. Wysocki
2017-04-11 12:20     ` Michal Hocko
2017-04-11 13:48       ` Rafael J. Wysocki
     [not found]         ` <CAJZ5v0hhoej=FoqYaBOwy1-_AP35WyEYYUNkb3Pn22G0monanA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-11 13:52           ` Michal Hocko
2017-04-11 13:54             ` Rafael J. Wysocki [this message]
     [not found]               ` <CAJZ5v0hzv1oxpNJvSc2omqaOFRgiBB8UKCbRKGkgzHbEtqosbQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-14 22:33                 ` Rafael J. Wysocki

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=CAJZ5v0hzv1oxpNJvSc2omqaOFRgiBB8UKCbRKGkgzHbEtqosbQ@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=jkosina@suse.cz \
    --cc=jlee@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=toshi.kani@hpe.com \
    /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).