From: Ingo Molnar <mingo@kernel.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] some scheduler code movements
Date: Thu, 22 Jun 2017 10:31:18 +0200 [thread overview]
Message-ID: <20170622083118.3ngmh27qg4x5kxho@gmail.com> (raw)
In-Reply-To: <20170621182203.30626-1-nicolas.pitre@linaro.org>
* Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> On Wed, 21 Jun 2017, Ingo Molnar wrote:
>
> > I've applied the first patch to the scheduler tree yesterday, but the other
> > changes unfortunately conflicted with other pending scheduler work - could
> > you please re-post the other 3 patches on top of tip:sched/core?
>
> Sure, here they are.
Hm, what tree is this against? First patch won't apply to the latest
tip:sched/core:
patching file kernel/sched/core.c
Hunk #7 succeeded at 5253 (offset -2 lines).
Hunk #8 FAILED at 5285.
Hunk #9 succeeded at 5581 (offset 1 line).
Hunk #10 succeeded at 6485 (offset 1 line).
1 out of 10 hunks FAILED -- rejects in file kernel/sched/core.c
Thanks,
Ingo
next prev parent reply other threads:[~2017-06-22 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 18:22 [PATCH 0/3] some scheduler code movements Nicolas Pitre
2017-06-21 18:22 ` [PATCH 1/3] sched/deadline: move dl related code out of sched/core.c Nicolas Pitre
2017-06-23 13:58 ` [tip:sched/core] sched/deadline: Move DL related code from sched/core.c to sched/deadline.c tip-bot for Nicolas Pitre
2017-06-21 18:22 ` [PATCH 2/3] sched/rt: move rt related code out of sched/core.c Nicolas Pitre
2017-06-23 13:59 ` [tip:sched/core] sched/rt: Move RT related code from sched/core.c to sched/rt.c tip-bot for Nicolas Pitre
2017-06-21 18:22 ` [PATCH 3/3] futex: split PI support to a file of its own Nicolas Pitre
2017-06-22 8:31 ` Ingo Molnar [this message]
2017-06-22 12:33 ` [PATCH 0/3] some scheduler code movements Nicolas Pitre
2017-06-22 14:07 ` Ingo Molnar
2017-06-22 17:19 ` Nicolas Pitre
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=20170622083118.3ngmh27qg4x5kxho@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicolas.pitre@linaro.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).