public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Clark Williams <williams@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] scheduler include file reorganization
Date: Fri, 8 Feb 2013 15:18:41 +0100	[thread overview]
Message-ID: <20130208141841.GB30334@gmail.com> (raw)
In-Reply-To: <20130207150838.02226207@riff.lan>


* Clark Williams <williams@redhat.com> wrote:

> On Thu, 7 Feb 2013 20:52:57 +0100
> Ingo Molnar <mingo@kernel.org> wrote:
> 
> > 
> > * Ingo Molnar <mingo@kernel.org> wrote:
> > 
> > > 
> > > * Ingo Molnar <mingo@kernel.org> wrote:
> > > 
> > > > Yeah, that looks pretty good.
> > > > 
> > > > I'll give it some testing.
> > > 
> > > Found one build error so far, applied the fix below.
> > 
> > Another one was in NOMMU mode (fixed below) - a hidden sched.h 
> > include file dependency in mm/nommu.c.
> > 
> > It's looking good otherwise!
> > 
> > Thanks,
> > 
> > 	Ingo
> >
> 
> Huh, I did a build with an allmodconfig config file. You must 
> be doing some odd permutations.

Yeah, randconfig coverage and cross-arch build coverage. One of 
the build errors triggered on allnoconfig, the other on the 
blackfin architecture.

> I have both of your fixes applied, send me any more you find 
> and I'll regenerate.

No need, I fixed your series locally and pushed out the result.

Wanna split out some other parts of sched.h? ;-) I can do the 
build coverage testing part for those as well.

Thanks,

	Ingo

  reply	other threads:[~2013-02-08 14:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 15:46 [PATCH 0/3] scheduler include file reorganization Clark Williams
2013-02-07 18:56 ` Ingo Molnar
2013-02-07 19:13   ` Ingo Molnar
2013-02-07 19:52     ` Ingo Molnar
2013-02-07 21:08       ` Clark Williams
2013-02-08 14:18         ` Ingo Molnar [this message]
2013-02-08 14:58           ` Clark Williams
2013-02-11  9:54             ` Ingo Molnar
2013-02-13  1:29               ` Namhyung Kim
2013-02-13  9:15                 ` Ingo Molnar
2013-02-13 15:19                   ` Clark Williams
2013-02-14  7:59                     ` Namhyung Kim
2013-02-16  3:40                   ` Li Zefan

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=20130208141841.GB30334@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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