From: Clark Williams <williams@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
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 08:58:28 -0600 [thread overview]
Message-ID: <20130208085828.02e61518@riff.lan> (raw)
In-Reply-To: <20130208141841.GB30334@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
On Fri, 8 Feb 2013 15:18:41 +0100
Ingo Molnar <mingo@kernel.org> wrote:
>
> * 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
I figured that was coming. :)
I'll look at it again and see about pulling the autogroup/cgroup stuff
into it's own header. After that it's probably going to require some
serious changes.
Any suggestions?
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-08 14:58 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
2013-02-08 14:58 ` Clark Williams [this message]
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=20130208085828.02e61518@riff.lan \
--to=williams@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.