linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [GIT pull] timers/core for 5.19-rc1
Date: Mon, 23 May 2022 17:11:12 -0700	[thread overview]
Message-ID: <CAHk-=wi0q-c95_OaHf9Eq16C7kURDNugdqBrE1wwXJf+yfX4Yw@mail.gmail.com> (raw)
In-Reply-To: <165329268338.3801280.15015388773053623832.tglx@xen13>

On Mon, May 23, 2022 at 1:02 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-2022-05-23

Hmm. My diffstat didn't match yours, and I couldn't figure out why,
until I noticed that:

> Anna-Maria Behnsen (3):
>       timers: Fix warning condition in __run_timers()

You had already sent this one to me as part of the timer fixes pull
back in mid-April, so it was already in my tree. Apparently you hadn't
updated upstream before doing the git request-pull script.

                   Linus

  reply	other threads:[~2022-05-24  0:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  8:02 [GIT pull] core/core for 5.19-rc1 Thomas Gleixner
2022-05-23  8:02 ` [GIT pull] core/debugobjects " Thomas Gleixner
2022-05-24  0:22   ` pr-tracker-bot
2022-05-23  8:02 ` [GIT pull] irq/core " Thomas Gleixner
2022-05-24  0:02   ` Linus Torvalds
2022-05-24  8:17     ` Thomas Gleixner
2022-05-24  0:22   ` pr-tracker-bot
2022-05-23  8:02 ` [GIT pull] smp/core " Thomas Gleixner
2022-05-24  0:22   ` pr-tracker-bot
2022-05-23  8:02 ` [GIT pull] timers/core " Thomas Gleixner
2022-05-24  0:11   ` Linus Torvalds [this message]
2022-05-24  8:07     ` Thomas Gleixner
2022-05-24  0:22   ` pr-tracker-bot
2022-05-23  8:02 ` [GIT pull] x86/irq " Thomas Gleixner
2022-05-24  0:22   ` pr-tracker-bot
2022-05-24  0:22 ` [GIT pull] core/core " pr-tracker-bot

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-=wi0q-c95_OaHf9Eq16C7kURDNugdqBrE1wwXJf+yfX4Yw@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).