linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] scheduler updates for 5.1
Date: Sun, 24 Mar 2019 19:39:43 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1903241929290.1798@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=wgC4FQeT8Z6+gXnbsDFxRAD9sSELd8-G=6gQg4kxKKL4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

On Sun, 24 Mar 2019, Linus Torvalds wrote:

> On Sun, Mar 24, 2019 at 7:14 AM Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > Second more careful attempt for this set of fixes:
> 
> What? No. It's the exact same garbage as last time, with no more care
> shown anywhere:
> 
>   kernel/sched/cpufreq_schedutil.c:346:26: note: in expansion of macro ‘min’
>      sg_cpu->iowait_boost = min(sg_cpu->iowait_boost << 1,
> SCHED_CAPACITY_SCALE);
> 
> I told you *exactly* what the problem was the last time, and it's
> *exactly* the same now too.
> 
> Hmm. Looking closer, I see that the patch you *claim* to send me has
> "min_t()". But the tree I actually got has the same old garbage.
> 
> I suspect you didn't update the git repo properly or something.

Duh. Just did

git checkout sched-urgent-for-linus
git diff sched/urgent	-> empty
git diff origin/sched/urgent -> empty
git diff origin/sched-urgent-for-linus -> empty

Now doing a fresh clone from git.k.org (not ssh) shows me the stale commit
from last week.

I'm sure that I force pushed and my pull request script checks whether all
branches are up to date before creating the pull request mail. No idea at
all what went wrong.

I just force pushed the thing once more. The head commit is:

  b9a7b8831600: sched/fair: Skip LLC NOHZ logic for asymmetric systems

I'll add that to the pull request mail scripts in future.

It has propagated to gitweb now as well.

Thanks,

	tglx

  reply	other threads:[~2019-03-24 18:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 14:12 [GIT pull] core updates for 5.1 Thomas Gleixner
2019-03-24 14:12 ` [GIT pull] timers " Thomas Gleixner
2019-03-24 18:40   ` pr-tracker-bot
2019-03-24 14:12 ` [GIT pull] irq " Thomas Gleixner
2019-03-24 18:40   ` pr-tracker-bot
2019-03-24 14:12 ` [GIT pull] perf " Thomas Gleixner
2019-03-24 18:40   ` pr-tracker-bot
2019-03-24 14:12 ` [GIT pull] x86 " Thomas Gleixner
2019-03-24 18:40   ` pr-tracker-bot
2019-03-24 14:12 ` [GIT pull] locking " Thomas Gleixner
2019-03-24 18:40   ` pr-tracker-bot
2019-03-24 14:12 ` [GIT pull] scheduler " Thomas Gleixner
2019-03-24 18:07   ` Linus Torvalds
2019-03-24 18:39     ` Thomas Gleixner [this message]
2019-03-24 18:48       ` Linus Torvalds
2019-03-24 19:01         ` Linus Torvalds
2019-03-24 18:40 ` [GIT pull] core " pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-03-10 11:33 [GIT pull] core udpate " Thomas Gleixner
2019-03-10 11:33 ` [GIT pull] scheduler updates " Thomas Gleixner
2019-03-10 20:56   ` Linus Torvalds
2019-03-11  9:09     ` Ingo Molnar
2019-03-11 14:16     ` Thomas Gleixner

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=alpine.DEB.2.21.1903241929290.1798@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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).