From: pr-tracker-bot@kernel.org
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org
Subject: Re: [GIT PULL] Move Arm documentation under Documentation/arch
Date: Tue, 27 Jun 2023 19:04:21 +0000 [thread overview]
Message-ID: <168789266115.16132.8218677774553892978.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <878rc4euln.fsf@meer.lwn.net>
The pull request you sent on Tue, 27 Jun 2023 10:30:12 -0600:
> git://git.lwn.net/linux.git tags/docs-arm-move
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/04fc8904d5d18a132f5ad67b79ee980b6602c8c6
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2023-06-27 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 16:30 [GIT PULL] Move Arm documentation under Documentation/arch Jonathan Corbet
2023-06-27 19:04 ` 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=168789266115.16132.8218677774553892978.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--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