From: pr-tracker-bot@kernel.org
To: Michal Simek <monstr@monstr.eu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze patches for 5.10-rc1
Date: Mon, 12 Oct 2020 18:21:04 +0000 [thread overview]
Message-ID: <160252686406.3643.5852027680568966470.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <bc40d653-7a72-973a-2b9e-8f3f6ca51fea@monstr.eu>
The pull request you sent on Mon, 12 Oct 2020 11:11:15 +0200:
> git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/024fb66772911a361279c03cd1f394b7a8fd3919
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2020-10-12 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 9:11 [GIT PULL] arch/microblaze patches for 5.10-rc1 Michal Simek
2020-10-12 18:21 ` 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=160252686406.3643.5852027680568966470.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--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;
as well as URLs for NNTP newsgroup(s).