From: pr-tracker-bot@kernel.org
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: torvalds@linux-foundation.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Second set of RISC-V updates for v5.5-rc1
Date: Wed, 04 Dec 2019 19:25:19 +0000 [thread overview]
Message-ID: <157548751994.30814.9638490489513007318.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1912040050430.56420@viisi.sifive.com>
The pull request you sent on Wed, 4 Dec 2019 00:52:08 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.5-rc1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6cdc7f2efc25a6dbddf7c57bb2eee5d6c033d678
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
WARNING: multiple messages have this Message-ID (diff)
From: pr-tracker-bot@kernel.org
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Second set of RISC-V updates for v5.5-rc1
Date: Wed, 04 Dec 2019 19:25:19 +0000 [thread overview]
Message-ID: <157548751994.30814.9638490489513007318.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1912040050430.56420@viisi.sifive.com>
The pull request you sent on Wed, 4 Dec 2019 00:52:08 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.5-rc1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6cdc7f2efc25a6dbddf7c57bb2eee5d6c033d678
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
next prev parent reply other threads:[~2019-12-04 19:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:52 [GIT PULL] Second set of RISC-V updates for v5.5-rc1 Paul Walmsley
2019-12-04 12:52 ` Anup Patel
2019-12-04 12:52 ` Anup Patel
2019-12-04 18:38 ` Alistair Francis
2019-12-04 18:38 ` Alistair Francis
2019-12-04 19:38 ` Paul Walmsley
2019-12-04 19:38 ` Paul Walmsley
2019-12-04 19:50 ` Alistair Francis
2019-12-04 19:50 ` Alistair Francis
2019-12-04 23:46 ` Anup Patel
2019-12-04 23:46 ` Anup Patel
2019-12-05 2:54 ` Paul Walmsley
2019-12-05 2:54 ` Paul Walmsley
2019-12-05 3:58 ` Alistair Francis
2019-12-05 3:58 ` Alistair Francis
2019-12-05 5:35 ` David Abdurachmanov
2019-12-05 5:35 ` David Abdurachmanov
2019-12-05 13:19 ` Anup Patel
2019-12-05 13:19 ` Anup Patel
2019-12-05 23:12 ` Paul Walmsley
2019-12-05 23:12 ` Paul Walmsley
2019-12-05 23:35 ` Alistair Francis
2019-12-05 23:35 ` Alistair Francis
2019-12-05 23:46 ` Alistair Francis
2019-12-05 23:46 ` Alistair Francis
2019-12-06 21:12 ` Carlos Eduardo de Paula
2019-12-06 21:12 ` Carlos Eduardo de Paula
2019-12-06 21:15 ` Anup Patel
2019-12-06 21:15 ` Anup Patel
2019-12-06 21:21 ` Carlos Eduardo de Paula
2019-12-06 21:21 ` Carlos Eduardo de Paula
2019-12-06 21:22 ` Linus Torvalds
2019-12-06 21:22 ` Linus Torvalds
2019-12-04 19:25 ` pr-tracker-bot [this message]
2019-12-04 19:25 ` pr-tracker-bot
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=157548751994.30814.9638490489513007318.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.