From: pr-tracker-bot@kernel.org
To: Olof Johansson <olof@lixom.net>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, soc@kernel.org,
arm@kernel.org, Olof Johansson <olof@lixom.net>
Subject: Re: [GIT PULL 2/4] ARM: SoC-related driver updates
Date: Thu, 05 Dec 2019 20:45:29 +0000 [thread overview]
Message-ID: <157557872948.26858.3177777574095454932.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20191205180453.14056-2-olof@lixom.net>
The pull request you sent on Thu, 5 Dec 2019 10:04:51 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-drivers
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ec939e4c94bd3ef2fd4f34c15f8aaf79bd0c5ee1
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: Olof Johansson <olof@lixom.net>
Cc: linux-kernel@vger.kernel.org, soc@kernel.org, arm@kernel.org,
Olof Johansson <olof@lixom.net>,
torvalds@linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/4] ARM: SoC-related driver updates
Date: Thu, 05 Dec 2019 20:45:29 +0000 [thread overview]
Message-ID: <157557872948.26858.3177777574095454932.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20191205180453.14056-2-olof@lixom.net>
The pull request you sent on Thu, 5 Dec 2019 10:04:51 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-drivers
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ec939e4c94bd3ef2fd4f34c15f8aaf79bd0c5ee1
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-12-05 20:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 18:04 [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2019-12-05 18:04 ` Olof Johansson
2019-12-05 18:04 ` [GIT PULL 2/4] ARM: SoC-related driver updates Olof Johansson
2019-12-05 18:04 ` Olof Johansson
2019-12-05 20:45 ` pr-tracker-bot [this message]
2019-12-05 20:45 ` pr-tracker-bot
2019-12-05 18:04 ` [GIT PULL 3/4] ARM: Device-tree updates Olof Johansson
2019-12-05 18:04 ` Olof Johansson
2019-12-05 20:45 ` pr-tracker-bot
2019-12-05 20:45 ` pr-tracker-bot
2019-12-05 18:04 ` [GIT PULL 4/4] ARM: SoC defconfig updates Olof Johansson
2019-12-05 18:04 ` Olof Johansson
2019-12-05 20:45 ` pr-tracker-bot
2019-12-05 20:45 ` pr-tracker-bot
2019-12-05 20:45 ` [GIT PULL 1/4] ARM: SoC platform updates pr-tracker-bot
2019-12-05 20:45 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-07-19 23:54 [GIT PULL 0/4] ARM: SoC contents for 5.3 merge window Olof Johansson
2019-07-19 23:54 ` [GIT PULL 2/4] ARM: SoC-related driver updates Olof Johansson
2019-07-19 23:54 ` Olof Johansson
2019-07-20 0:06 ` Olof Johansson
2019-07-20 0:06 ` Olof Johansson
2019-07-20 0:30 ` pr-tracker-bot
2019-07-20 0:30 ` 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=157557872948.26858.3177777574095454932.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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 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.