From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
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 12:01:20 -0700 [thread overview]
Message-ID: <CAHk-=whM4WVADKr_Qg-5nv8UczLp+eBd6KH44y_6=XC4nvvrcQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wixSEaRjAPT8ZiJhbs-5phzjSrRktz7tOCdSe5OCixfmA@mail.gmail.com>
On Sun, Mar 24, 2019 at 11:48 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> It looks right to me now, so I've pulled it.
Interestingly, I'm not seeing pr-tracker-bot reacting to my pull.
I *think* that's because pr-tracker-bot saw the same thing as I
initially did for the pull request, so it thinks the pull I actually
*did* after you force-updated the branch doesn't match the original
pull request, because I ended up pulling something else..
Or maybe it's just delayed. We'll see.
Linus
next prev parent reply other threads:[~2019-03-24 19:01 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
2019-03-24 18:48 ` Linus Torvalds
2019-03-24 19:01 ` Linus Torvalds [this message]
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='CAHk-=whM4WVADKr_Qg-5nv8UczLp+eBd6KH44y_6=XC4nvvrcQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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).