From: Greg KH <gregkh@linuxfoundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: stable kernel team <stable@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [tip:smp/urgent] hotplug: Make register and unregister notifier API symmetric
Date: Tue, 13 Dec 2016 14:25:21 -0800 [thread overview]
Message-ID: <20161213222521.GA28477@kroah.com> (raw)
In-Reply-To: <20161213205038.GA13917@gmail.com>
On Tue, Dec 13, 2016 at 09:50:38PM +0100, Ingo Molnar wrote:
>
> * Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > On Tue, Dec 13, 2016 at 07:39:58AM +0100, Ingo Molnar wrote:
> > >
> > > hi Greg,
> > >
> > > Please apply this fix to v4.9-stable as well, it's now upstream.
> >
> > Ok, it looks like it belongs in older stable kernels as well, based on
> > the fixes: tag, correct?
>
> Yes, indeed - but the testing was v4.9 based and there's been all sorts of changes
> in the CPU hotplug machinery.
>
> The fixes tag:
>
> > > Fixes: 47e627bc8c9a ("[PATCH] hotplug: Allow modules to use the cpu hotplug notifiers even if !CONFIG_HOTPLUG_CPU")
>
> Suggests it's an ancient bug and 777c6e0daebb3fce cherry-picks fine as far back as
> v4.6.
As 47e627bc8c9a was in 2.6.21, I did the trivial fixup and applied it to
4.4-stable as well.
thanks,
greg k-h
next prev parent reply other threads:[~2016-12-13 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 6:39 [tip:smp/urgent] hotplug: Make register and unregister notifier API symmetric Ingo Molnar
2016-12-13 12:18 ` Greg KH
2016-12-13 20:50 ` Ingo Molnar
2016-12-13 20:52 ` Thomas Gleixner
2016-12-13 22:25 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-07 13:54 [PATCH] hotplug: make " Michal Hocko
2016-12-08 9:13 ` [tip:smp/urgent] hotplug: Make " tip-bot for Michal Hocko
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=20161213222521.GA28477@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.