public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org, vatsa@in.ibm.com,
	bharata@linux.vnet.ibm.com, dhaval@linux.vnet.ibm.com
Subject: Re: [PATCH v2] sched: add uid information to sched_debug for CONFIG_USER_SCHED
Date: Mon, 1 Dec 2008 20:40:07 +0100	[thread overview]
Message-ID: <20081201194007.GC17250@elte.hu> (raw)
In-Reply-To: <20081201151905.GA8448@linux.vnet.ibm.com>


* Arun R Bharadwaj <arun@linux.vnet.ibm.com> wrote:

> * Ingo Molnar <mingo@elte.hu> [2008-12-01 13:56:28]:
> 
> > 
> > * Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > 
> > > * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > > 
> > > > On Mon, 2008-12-01 at 16:59 +0530, Arun R Bharadwaj wrote:
> > > > > Hi,
> > > > > 
> > > > > This patch adds uid information in sched_debug for CONFIG_USER_SCHED
> > > > 
> > > > I'd much rather have people working at removing USER_SCHED,. but sure,
> > > > the patch looks sane..
> > > 
> > > ok, i have applied it to tip/sched/core.
> > 
> > it doesnt build:
> > 
> >  kernel/sched_debug.c: In function 'print_cfs_rq':
> >  kernel/sched_debug.c:165: error: 'struct cfs_rq' has no member named 'tg'
> > 
> > please send v2 patch.
> > 
> > Ingo
> 
> Hi Ingo,
> 
> I've posted v2 of the patch.
> Had missed an '&& #if defined(CONFIG_FAIR_GROUP_SCHED)' last time
> around.

applied, thanks!

	Ingo

      reply	other threads:[~2008-12-01 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 11:29 [PATCH] sched: add uid information to sched_debug for CONFIG_USER_SCHED Arun R Bharadwaj
2008-12-01 11:36 ` Peter Zijlstra
2008-12-01 12:44   ` Ingo Molnar
2008-12-01 12:56     ` Ingo Molnar
2008-12-01 15:19       ` [PATCH v2] " Arun R Bharadwaj
2008-12-01 19:40         ` Ingo Molnar [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=20081201194007.GC17250@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vatsa@in.ibm.com \
    /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