linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 16:07:26 +0200	[thread overview]
Message-ID: <20170622140726.qy75pskkg5r3q4wa@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1706220825200.29475@knanqh.ubzr>


* Nicolas Pitre <nicolas.pitre@linaro.org> wrote:

> On Thu, 22 Jun 2017, Ingo Molnar wrote:
> 
> > 
> > * 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
> 
> That's against my copy of tip/sched/core as of yesterday:
> 
> commit f11cc0760b8397e0d230122606421b6a96e9f869
> Author:     Davidlohr Bueso <dave@stgolabs.net>
> AuthorDate: Wed Jun 14 19:37:30 2017 -0700
> Commit:     Ingo Molnar <mingo@kernel.org>
> CommitDate: Tue Jun 20 12:48:37 2017 +0200
> 
>     sched/core: Drop the unused try_get_task_struct() helper function
> 
> on which I pre-applied my previous patch #1/4 ("cpuset/sched: cpuset 
> makes sense for SMP only") you said having already applied on your side 
> but that didn't show up in the publicly visible sched/core yet.

I see where the mismatch comes from - I applied this one from your earlier 
patches:

  f5832c1998af: sched/core: Omit building stop_sched_class when !SMP

... thus #1/4 was missing from my stack of patches. I'll apply that too and 
re-try, no need to resend.

Thanks,

	Ingo

  reply	other threads:[~2017-06-22 14:07 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 ` [PATCH 0/3] some scheduler code movements Ingo Molnar
2017-06-22 12:33   ` Nicolas Pitre
2017-06-22 14:07     ` Ingo Molnar [this message]
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=20170622140726.qy75pskkg5r3q4wa@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).