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 -rc6
Date: Fri, 23 Feb 2024 18:44:07 +0000 [thread overview]
Message-ID: <170871384747.26987.14345883877585633830.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20240223102531.GB10274@willie-the-truck>
The pull request you sent on Fri, 23 Feb 2024 10:25:32 +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/86f01602a41fb711f992ad6ab6483a4487829b4c
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
WARNING: multiple messages have this Message-ID (diff)
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 -rc6
Date: Fri, 23 Feb 2024 18:44:07 +0000 [thread overview]
Message-ID: <170871384747.26987.14345883877585633830.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20240223102531.GB10274@willie-the-truck>
The pull request you sent on Fri, 23 Feb 2024 10:25:32 +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/86f01602a41fb711f992ad6ab6483a4487829b4c
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:[~2024-02-23 18:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 10:25 [GIT PULL] arm64 fixes for -rc6 Will Deacon
2024-02-23 10:25 ` Will Deacon
2024-02-23 18:44 ` pr-tracker-bot [this message]
2024-02-23 18:44 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-06-08 20:51 Will Deacon
2023-06-08 20:51 ` Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2023-06-08 21:49 ` pr-tracker-bot
2021-12-15 11:19 Will Deacon
2021-12-15 11:19 ` Will Deacon
2021-12-15 16:00 ` Catalin Marinas
2021-12-15 16:00 ` Catalin Marinas
2021-12-15 18:49 ` Linus Torvalds
2021-12-15 18:49 ` Linus Torvalds
2020-11-27 11:40 Will Deacon
2020-11-27 11:40 ` Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 15:20 ` Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 14:32 ` Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 12:12 ` Will Deacon
2019-08-24 12:12 ` Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-08-24 18:45 ` pr-tracker-bot
2019-08-24 18:45 ` pr-tracker-bot
2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon
2019-06-20 16:59 ` Will Deacon
2019-06-20 19:10 ` pr-tracker-bot
2019-06-20 19:10 ` pr-tracker-bot
2019-02-08 17:35 Will Deacon
2019-02-08 17:35 ` Will Deacon
2019-02-09 0:40 ` pr-tracker-bot
2019-02-09 0:40 ` pr-tracker-bot
2017-04-07 16:02 Will Deacon
2017-04-07 16:02 ` Will Deacon
2017-04-11 19:12 ` Jon Masters
2017-04-11 19:12 ` Jon Masters
2017-04-12 9:14 ` Will Deacon
2017-04-12 9:14 ` Will Deacon
2017-04-12 10:18 ` Punit Agrawal
2017-04-12 10:18 ` Punit Agrawal
2015-10-15 13:38 Will Deacon
2015-10-15 13:38 ` Will Deacon
2015-01-23 16:44 Will Deacon
2015-01-23 16:44 ` 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=170871384747.26987.14345883877585633830.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 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.