From: pr-tracker-bot@kernel.org
To: Will Deacon <will@kernel.org>
Cc: torvalds@linux-foundation.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [GIT PULL] arm64 fixes for -rc1
Date: Fri, 16 Dec 2022 19:50:16 +0000 [thread overview]
Message-ID: <167122021617.13335.8884134192467234426.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20221216155111.GA8949@willie-the-truck>
The pull request you sent on Fri, 16 Dec 2022 15:51:13 +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/77856d911a8c8724ee8e2b09d55979fc1de8f1c0
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
_______________________________________________
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:[~2022-12-16 19:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 15:51 [GIT PULL] arm64 fixes for -rc1 Will Deacon
2022-12-16 19:50 ` pr-tracker-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 16:05 Will Deacon
2024-01-19 16:34 ` Rob Herring
2024-01-19 16:58 ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2023-05-04 14:22 Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2017-03-01 4:51 [GIT PULL] arm64 " Will Deacon
2016-08-05 15:48 [GIT PULL] arm64: " Will Deacon
2014-12-16 17:50 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=167122021617.13335.8884134192467234426.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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).