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] x86/cpu for 6.1
Date: Tue, 04 Oct 2022 17:34:05 +0000 [thread overview]
Message-ID: <166490484500.22164.1786201671630735821.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <YzvzxYCBAPX47PTf@zn.tnic>
The pull request you sent on Tue, 4 Oct 2022 10:50:13 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cpu_for_v6.1_rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7db99f01d1879f30af95f14dfd5cbcf009d15166
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2022-10-04 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 8:50 [GIT PULL] x86/cpu for 6.1 Borislav Petkov
2022-10-04 17:34 ` 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=166490484500.22164.1786201671630735821.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).