From: pr-tracker-bot@kernel.org
To: Will Deacon <will.deacon@arm.com>
Cc: catalin.marinas@arm.com, lorenzo.pieralisi@arm.com,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] arm64: fixes for -rc2
Date: Fri, 11 Jan 2019 20:40:01 +0000 [thread overview]
Message-ID: <154723920158.6200.7472731315707078708.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20190111182057.GB32645@fuggles.cambridge.arm.com>
The pull request you sent on Fri, 11 Jan 2019 18:20:57 +0000:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c3405d689974555532c12a4f3a5e72dedc660c0b
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-11 20:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 18:20 [GIT PULL] arm64: fixes for -rc2 Will Deacon
2019-01-11 20:40 ` pr-tracker-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 16:29 [GIT PULL] arm64 " Will Deacon
2022-04-08 17:46 ` pr-tracker-bot
2021-07-16 14:53 Will Deacon
2021-07-17 2:12 ` pr-tracker-bot
2020-10-30 17:05 Will Deacon
2020-10-30 20:29 ` pr-tracker-bot
2020-06-19 12:43 Will Deacon
2020-06-19 19:30 ` pr-tracker-bot
2020-02-13 17:10 Will Deacon
2020-02-13 22:40 ` pr-tracker-bot
2019-07-26 13:12 [GIT PULL] arm64: " Will Deacon
2019-07-26 18:25 ` pr-tracker-bot
2018-08-31 16:12 Will Deacon
2017-12-01 18:23 Will Deacon
2016-10-20 17:14 Will Deacon
2016-06-03 15:37 Will Deacon
2016-04-01 15:15 Will Deacon
2016-01-27 18:45 Will Deacon
2015-09-17 14:04 Will Deacon
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=154723920158.6200.7472731315707078708.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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).