From: pr-tracker-bot@kernel.org
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] locking/core for v5.17
Date: Wed, 12 Jan 2022 01:35:51 +0000 [thread overview]
Message-ID: <164195135149.30057.9627466230188569494.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <Yd2/yMnHa8zHe02U@zn.tnic>
The pull request you sent on Tue, 11 Jan 2022 18:35:04 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/locking_core_for_v5.17_rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/daadb3bd0e8d3e317e36bc2c1542e86c528665e5
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2022-01-12 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 17:35 [GIT PULL] locking/core for v5.17 Borislav Petkov
2022-01-12 1:35 ` pr-tracker-bot [this message]
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=164195135149.30057.9627466230188569494.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=bp@suse.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).