All of lore.kernel.org
 help / color / mirror / Atom feed
From: pr-tracker-bot@kernel.org
To: Olof Johansson <olof@lixom.net>
Cc: torvalds@linux-foundation.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, arm@kernel.org,
	Olof Johansson <olof@lixom.net>
Subject: Re: [GIT PULL 2/4] ARM: SoC driver updates
Date: Tue, 01 Jan 2019 01:45:04 +0000	[thread overview]
Message-ID: <20190101014504.19922.13368.pr-tracker-bot@pdx-korg-gitolite-1.ci.codeaurora.org> (raw)
In-Reply-To: <20181231214640.17015-3-olof@lixom.net>

The pull request you sent on Mon, 31 Dec 2018 13:46:38 -0800:

> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-drivers

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d36377c6eb071e3d0751e9e0e3c19198c58d9a5d

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: Olof Johansson <olof@lixom.net>,
	arm@kernel.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/4] ARM: SoC driver updates
Date: Tue, 01 Jan 2019 01:45:04 +0000	[thread overview]
Message-ID: <20190101014504.19922.13368.pr-tracker-bot@pdx-korg-gitolite-1.ci.codeaurora.org> (raw)
In-Reply-To: <20181231214640.17015-3-olof@lixom.net>

The pull request you sent on Mon, 31 Dec 2018 13:46:38 -0800:

> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-drivers

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d36377c6eb071e3d0751e9e0e3c19198c58d9a5d

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

  reply	other threads:[~2019-01-01  1:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31 21:46 [GIT PULL 0/4] ARM: SoC changes for v4.21 Olof Johansson
2018-12-31 21:46 ` Olof Johansson
2018-12-31 21:46 ` [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot
2018-12-31 21:46 ` [GIT PULL 2/4] ARM: SoC driver updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot [this message]
2019-01-01  1:45     ` pr-tracker-bot
2018-12-31 21:46 ` [GIT PULL 3/4] ARM: Device-tree updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot
2018-12-31 21:46 ` [GIT PULL 4/4] ARM: SoC defconfig updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2018-08-23  4:32 [GIT PULL 0/4] ARM: SoC/platform updates Olof Johansson
2018-08-23  4:32 ` [GIT PULL 2/4] ARM: SoC driver updates Olof Johansson
2018-08-23  4:32   ` Olof Johansson

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=20190101014504.19922.13368.pr-tracker-bot@pdx-korg-gitolite-1.ci.codeaurora.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=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.