From: pr-tracker-bot@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
SoC Team <soc@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 4/6] ARM: SoC defconfig updates for 5.20
Date: Tue, 02 Aug 2022 16:39:06 +0000 [thread overview]
Message-ID: <165945834696.26510.4813587390738921717.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <CAK8P3a2VY8n16XU6+dxxGPSO0gkCwd8JiMj-g_8g-cG4ayWcyA@mail.gmail.com>
The pull request you sent on Fri, 29 Jul 2022 00:32:42 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/arm-defconfig-5.20
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3a829d267e10812e3b2c2d656ba9fdc117ea6579
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-08-02 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 22:28 [GIT PULL 0/6] SoC branches for 5.20 Arnd Bergmann
2022-07-28 22:29 ` [GIT PULL 1/6] ARM: SoC updates " Arnd Bergmann
2022-08-01 15:29 ` Linus Torvalds
2022-08-02 16:39 ` pr-tracker-bot
2022-07-28 22:32 ` [GIT PULL 4/6] ARM: SoC defconfig " Arnd Bergmann
2022-08-02 16:39 ` pr-tracker-bot [this message]
2022-07-28 22:35 ` [GIT PULL 5/6] ARM: new SoC support " Arnd Bergmann
2022-08-02 16:39 ` pr-tracker-bot
2022-07-28 22:36 ` [GIT PULL 6/6] ARM: boardfile deprecation " Arnd Bergmann
2022-08-02 16:39 ` pr-tracker-bot
2022-07-28 23:15 ` [GIT PULL 0/6] SoC branches " Linus Torvalds
2022-07-29 7:15 ` Arnd Bergmann
2022-07-29 16:15 ` Linus Torvalds
2022-07-30 9:49 ` Arnd Bergmann
2022-08-02 16:39 ` pr-tracker-bot
2022-07-29 7:13 ` [GIT PULL 2/6, resend] ARM: DT changes " Arnd Bergmann
2022-08-02 16:39 ` 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=165945834696.26510.4813587390738921717.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=arnd@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--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).