From: Peter Zijlstra <peterz@infradead.org>
To: josef@toxicpanda.com
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
Josef Bacik <jbacik@fb.com>
Subject: Re: [PATCH] sched/fair: move definitions to fix !CONFIG_SMP
Date: Mon, 21 Aug 2017 22:06:53 +0200 [thread overview]
Message-ID: <20170821200653.GC32112@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1503345785-9323-1-git-send-email-jbacik@fb.com>
On Mon, Aug 21, 2017 at 04:03:05PM -0400, josef@toxicpanda.com wrote:
> From: Josef Bacik <jbacik@fb.com>
>
> The series of patches adding runnable_avg and subsequent supporting
> patches broke on !CONFIG_SMP. Fix this by moving the definitions under
> the appropriate checks, and moving the !CONFIG_SMP definitions higher
> up.
Is this on top or can I fold this in somewhere? I was meaning to rework
the series to avoid this superfluous build borkage.
next prev parent reply other threads:[~2017-08-21 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 20:03 [PATCH] sched/fair: move definitions to fix !CONFIG_SMP josef
2017-08-21 20:06 ` Peter Zijlstra [this message]
2017-08-21 20:44 ` Josef Bacik
2017-08-21 20:20 ` Josef Bacik
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=20170821200653.GC32112@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jbacik@fb.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox