linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: pr-tracker-bot@kernel.org
To: Stephen Boyd <sboyd@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clk changes for the merge window
Date: Thu, 08 Jul 2021 19:49:19 +0000	[thread overview]
Message-ID: <162577375919.18035.2259842155066295152.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20210708001431.437073-1-sboyd@kernel.org>

The pull request you sent on Wed,  7 Jul 2021 17:14:31 -0700:

> https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-for-linus

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

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

  reply	other threads:[~2021-07-08 19:49 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  0:14 [GIT PULL] clk changes for the merge window Stephen Boyd
2021-07-08 19:49 ` pr-tracker-bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-14 19:43 Stephen Boyd
2024-03-15 18:54 ` Linus Torvalds
2024-03-15 20:37 ` pr-tracker-bot
2024-01-09 22:39 Stephen Boyd
2024-01-12 22:20 ` pr-tracker-bot
2023-10-31 21:30 Stephen Boyd
2023-11-01  4:54 ` pr-tracker-bot
2023-08-31  1:14 Stephen Boyd
2023-08-31  3:20 ` pr-tracker-bot
2023-06-27  5:11 Stephen Boyd
2023-06-29 17:34 ` pr-tracker-bot
2023-05-07  0:27 Stephen Boyd
2023-05-07 18:12 ` pr-tracker-bot
2023-04-29  1:25 Stephen Boyd
2023-04-30  0:52 ` pr-tracker-bot
2023-02-25  4:45 Stephen Boyd
2023-02-25 23:22 ` pr-tracker-bot
2022-12-13 21:17 Stephen Boyd
2022-12-13 21:54 ` pr-tracker-bot
2022-10-07 20:58 Stephen Boyd
2022-10-08 17:35 ` pr-tracker-bot
2022-08-05  0:10 Stephen Boyd
2022-08-05  1:50 ` pr-tracker-bot
2022-05-26 23:57 Stephen Boyd
2022-05-27 22:45 ` pr-tracker-bot
2022-03-29 21:27 Stephen Boyd
2022-03-30 18:20 ` pr-tracker-bot
2022-01-12 21:28 Stephen Boyd
2022-01-13  1:10 ` pr-tracker-bot
2021-11-04  0:48 Stephen Boyd
2021-11-04  4:28 ` pr-tracker-bot
2021-09-02 19:07 Stephen Boyd
2021-09-02 22:42 ` pr-tracker-bot
2021-06-30 18:38 Stephen Boyd
2021-07-01 21:58 ` pr-tracker-bot
2021-04-28 23:57 Stephen Boyd
2021-04-29  0:26 ` pr-tracker-bot
2021-02-19 19:55 Stephen Boyd
2021-02-22 18:11 ` pr-tracker-bot
2020-12-21  1:52 Stephen Boyd
2020-12-21 18:45 ` Linus Torvalds
2020-12-21 18:46 ` pr-tracker-bot
2020-10-22 18:48 Stephen Boyd
2020-10-22 20:04 ` pr-tracker-bot
2020-08-07 20:02 Stephen Boyd
2020-08-07 20:39 ` pr-tracker-bot
2020-06-09 22:53 Stephen Boyd
2020-06-10 18:55 ` pr-tracker-bot
2020-04-05  2:53 Stephen Boyd
2020-04-05 19:45 ` pr-tracker-bot
2020-02-03 19:38 Stephen Boyd
2020-02-03 22:35 ` pr-tracker-bot
2019-11-27 21:36 Stephen Boyd
2019-12-02  2:05 ` pr-tracker-bot
2019-09-20 21:40 Stephen Boyd
2019-09-20 23:00 ` pr-tracker-bot
2019-07-16 17:15 Stephen Boyd
2019-07-17 17:15 ` pr-tracker-bot
2019-05-09 21:15 Stephen Boyd
2019-05-09 22:15 ` pr-tracker-bot
2019-03-13 18:28 Stephen Boyd
2019-03-14 17:55 ` pr-tracker-bot
2018-12-21 21:34 Stephen Boyd
2018-12-25 23:20 ` 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=162577375919.18035.2259842155066295152.pr-tracker-bot@kernel.org \
    --to=pr-tracker-bot@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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).