From: pr-tracker-bot@kernel.org
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mm-commits@vger.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.3
Date: Thu, 20 Apr 2023 01:25:20 +0000 [thread overview]
Message-ID: <168195392025.1989.12917488404470266327.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20230419163823.f2a0f64f0ef67ddee54c2461@linux-foundation.org>
The pull request you sent on Wed, 19 Apr 2023 16:38:23 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2023-04-19-16-36
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cb0856346a60fe3eb837ba5e73588a41f81ac05f
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2023-04-20 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 23:38 Andrew Morton
2023-04-20 1:25 ` 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=168195392025.1989.12917488404470266327.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.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