linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Mike Galbraith <mgalbraith@suse.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Make schedstats a runtime tunable that is disabled by default
Date: Mon, 25 Jan 2016 16:46:33 +0000	[thread overview]
Message-ID: <20160125164633.GG3162@techsingularity.net> (raw)
In-Reply-To: <20160125152908.GC2723@codeblueprint.co.uk>

On Mon, Jan 25, 2016 at 03:29:08PM +0000, Matt Fleming wrote:
> On Mon, 25 Jan, at 10:05:31AM, Mel Gorman wrote:
> > +static int __init setup_schedstats(char *str)
> > +{
> > +	int ret = 0;
> > +	if (!str)
> > +		goto out;
> > +
> > +	if (!strcmp(str, "enable")) {
> > +		set_schedstats(true);
> > +		ret = 1;
> > +	} else if (!strcmp(str, "disable")) {
> > +		set_schedstats(false);
> > +		ret = 1;
> > +	}
> > +out:
> > +	if (!ret)
> > +		pr_warn("Unable to parse numa_balancing=\n");
> > +
> 
> Copy+paste error?

Yes.

-- 
Mel Gorman
SUSE Labs

      reply	other threads:[~2016-01-25 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 10:05 [PATCH] sched: Make schedstats a runtime tunable that is disabled by default Mel Gorman
2016-01-25 11:26 ` Peter Zijlstra
2016-01-25 13:39   ` Mel Gorman
2016-01-25 14:59     ` Peter Zijlstra
2016-01-25 15:46       ` Ingo Molnar
2016-01-25 17:07         ` Mel Gorman
2016-01-25 18:40           ` Ingo Molnar
2016-01-25 20:11             ` Mel Gorman
2016-01-25 20:45               ` Mel Gorman
2016-01-26  8:13                 ` Ingo Molnar
2016-01-25 17:05       ` Mel Gorman
2016-01-25 15:29 ` Matt Fleming
2016-01-25 16:46   ` Mel Gorman [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=20160125164633.GG3162@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mgalbraith@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).