From: Phil Auld <pauld@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, bsegall@google.com,
torvalds@linux-foundation.org, anton@ozlabs.org, efault@gmx.de,
mingo@kernel.org, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched/fair: Limit sched_cfs_period_timer loop to avoid hard lockup
Date: Tue, 9 Apr 2019 09:15:38 -0400 [thread overview]
Message-ID: <20190409131537.GC10132@pauld.bos.csb> (raw)
In-Reply-To: <20190409130527.GR11158@hirez.programming.kicks-ass.net>
On Tue, Apr 09, 2019 at 03:05:27PM +0200 Peter Zijlstra wrote:
> On Tue, Apr 09, 2019 at 08:48:16AM -0400, Phil Auld wrote:
> > Hi Ingo, Peter,
> >
> > On Wed, Apr 03, 2019 at 01:38:39AM -0700 tip-bot for Phil Auld wrote:
> > > Commit-ID: 06ec5d30e8d57b820d44df6340dcb25010d6d0fa
> > > Gitweb: https://git.kernel.org/tip/06ec5d30e8d57b820d44df6340dcb25010d6d0fa
> > > Author: Phil Auld <pauld@redhat.com>
> > > AuthorDate: Tue, 19 Mar 2019 09:00:05 -0400
> > > Committer: Ingo Molnar <mingo@kernel.org>
> > > CommitDate: Wed, 3 Apr 2019 09:50:23 +0200
> >
> > This commit seems to have gotten lost. It's not in tip and now the
> > direct gitweb link is also showing bad commit reference.
> >
> > Did this fall victim to a reset or something?
>
> It had (trivial) builds fails on 32 bit. I have a fixed up version
> around somewhere, but that hasn't made it back in yet.
Drat. Sorry about that. At least I'm not going crazy...
Do you want me to fix it and push it back or will you do that?
Thanks,
Phil
--
next prev parent reply other threads:[~2019-04-09 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:00 [PATCH v2] sched/fair: Limit sched_cfs_period_timer loop to avoid hard lockup Phil Auld
2019-03-21 18:01 ` Peter Zijlstra
2019-03-21 18:32 ` Phil Auld
2019-04-03 8:38 ` [tip:sched/core] " tip-bot for Phil Auld
2019-04-09 12:48 ` Phil Auld
2019-04-09 13:05 ` Peter Zijlstra
2019-04-09 13:15 ` Phil Auld [this message]
2019-04-16 13:33 ` Phil Auld
2019-04-16 16:18 ` Phil Auld
2019-04-16 15:32 ` [tip:sched/urgent] sched/fair: Limit sched_cfs_period_timer() " tip-bot for Phil Auld
2019-04-16 19:26 ` Phil Auld
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=20190409131537.GC10132@pauld.bos.csb \
--to=pauld@redhat.com \
--cc=anton@ozlabs.org \
--cc=bsegall@google.com \
--cc=efault@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox