From: pr-tracker-bot@kernel.org
To: Stafford Horne <shorne@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [GIT PULL] OpenRISC updates for v5.6
Date: Tue, 07 Apr 2020 19:55:25 +0000 [thread overview]
Message-ID: <158628932584.3792.16656826106512591465.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20200407121628.GP7926@lianli.shorne-pla.net>
The pull request you sent on Tue, 7 Apr 2020 21:16:28 +0900:
> git://github.com/openrisc/linux.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d5d247661e869b71e4db5ca69b08b9607895d496
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
next prev parent reply other threads:[~2020-04-07 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 12:16 [GIT PULL] OpenRISC updates for v5.6 Stafford Horne
2020-04-07 19:55 ` pr-tracker-bot [this message]
2020-04-07 12:19 Stafford Horne
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=158628932584.3792.16656826106512591465.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.com \
--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).