From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ben Pineau <benjamin.pineau@mirakl.com>,
Ingo Molnar <mingo@kernel.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Two sched patchs missing from 4.4-stable: inclusion possible?
Date: Tue, 23 May 2017 12:27:12 +0200 [thread overview]
Message-ID: <20170523102712.GF28565@kroah.com> (raw)
In-Reply-To: <20170518105103.locuxtyazicdnf4y@hirez.programming.kicks-ass.net>
On Thu, May 18, 2017 at 12:51:03PM +0200, Peter Zijlstra wrote:
> On Thu, May 18, 2017 at 11:35:00AM +0200, Greg KH wrote:
> > On Thu, May 18, 2017 at 11:11:23AM +0200, Ben Pineau wrote:
> > > Hello,
> > >
> > > The following two patches series, merged in mainline 4.7, was Cc'ed to stable@,
> > > but somehow didn't made its way to the 4.4.x stable tree:
> > > 754bd598be9bbc953bc709a9e8ed7f3188bfb9d7
> > > 094f469172e00d6ab0a3130b0e01c83b3cf3a98d
>
> It would be so much easier if that were normal quotes like:
>
> 754bd598be9b ("sched/fair: Do not announce throttled next buddy in dequeue_task_fair()")
> 094f469172e0 ("sched/fair: Initialize throttle_count for new task-groups lazily")
>
> Then I'd not have had to look them up. And I'm most certainly not going
> to click through various interweb sites to provide answers.
>
> > Sure, I'll be glad to take them if I can get an ack from the patch
> > authors, and reviewers (added to: and cc:)...
> >
> > Ingo and Peter, any objections?
>
> No, those patches should be fine I think.
Thanks, now queued up.
greg k-h
prev parent reply other threads:[~2017-05-23 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:11 Two sched patchs missing from 4.4-stable: inclusion possible? Ben Pineau
2017-05-18 9:35 ` Greg KH
2017-05-18 10:51 ` Peter Zijlstra
2017-05-23 10:27 ` Greg KH [this message]
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=20170523102712.GF28565@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.pineau@mirakl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
/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.