Linux clock framework development
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
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, 25 Jun 2026 11:46:25 -0400	[thread overview]
Message-ID: <aj1NUYRrD30ctAbt@redhat.com> (raw)
In-Reply-To: <20260625151438.8471-1-sboyd@kernel.org>

Hey Stephen,

On Thu, Jun 25, 2026 at 08:14:37AM -0700, Stephen Boyd wrote:
> The following changes since commit 2abdc3dcf9780d070e55a99fdf8f93440c798b84:
> 
>   dt-bindings: clock: renesas,cpg-clocks: Document ZT/ZTR trace clock on R-Mobile APE6 (2026-05-15 11:26:26 +0200)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-for-linus
> 
> for you to fetch changes up to 92010229c4b38897f1319d260162d2f96925ed17:
> 
>   Merge branches 'clk-microchip' and 'clk-qcom' into clk-next (2026-06-25 07:55:47 -0700)
> 
> ----------------------------------------------------------------
> This is all clk driver updates. Mostly new SoC support for
> various Qualcomm chips and Canaan K230. Otherwise there's
> non-critical fixes and updates to clk data such as adding missing
> clks to existing drivers or marking clks critical. Nothing looks
> especially exciting.
> 
> ----------------------------------------------------------------

Would it be possible to also include Benoît's support for the Mobileye EyeQ7H
SoC? He has a pull ready:

https://lore.kernel.org/linux-clk/h_BA0KRKTGSANQ5Y4eqo6A@bootlin.com/

This also wasn't picked up during the last merge window. We push vendors to
upstream their code, and they point to situations like this when they tell
us it's too hard to upstream their code.

It looks like this was mostly pulls from the subsystems under clk. There's
also a bunch of patch sets that I reviewed this development cycle that I feel
should have been picked up. I'll send you a pull for that.

Brian


  reply	other threads:[~2026-06-25 15:46 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 15:14 [GIT PULL] clk changes for the merge window Stephen Boyd
2026-06-25 15:46 ` Brian Masney [this message]
2026-06-25 19:57 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-04-20 18:32 Stephen Boyd
2026-04-21 14:18 ` Brian Masney
2026-04-23 10:21   ` Brian Masney
2026-04-21 15:45 ` Linus Torvalds
2026-04-25 17:30   ` Stephen Boyd
2026-04-25 18:19     ` Linus Torvalds
2026-04-21 16:25 ` pr-tracker-bot
2026-02-15  1:53 Stephen Boyd
2026-02-15 16:57 ` pr-tracker-bot
2025-12-07 20:41 Stephen Boyd
2025-12-08  0:40 ` pr-tracker-bot
2025-10-07  5:17 Stephen Boyd
2025-10-07 18:39 ` pr-tracker-bot
2025-07-31 16:43 Stephen Boyd
2025-07-31 20:51 ` pr-tracker-bot
2025-05-30  0:14 Stephen Boyd
2025-05-30 17:29 ` pr-tracker-bot
2025-03-28 20:53 Stephen Boyd
2025-03-30  2:39 ` pr-tracker-bot
2025-01-22  0:23 Stephen Boyd
2025-01-22 19:06 ` pr-tracker-bot
2024-11-21 22:45 Stephen Boyd
2024-11-23  1:31 ` pr-tracker-bot
2024-09-23 18:29 Stephen Boyd
2024-09-23 22:19 ` Linus Torvalds
2024-09-23 22:34 ` pr-tracker-bot
2024-07-18 20:25 Stephen Boyd
2024-07-19 19:38 ` pr-tracker-bot
2024-05-17  1:31 Stephen Boyd
2024-05-18 21:06 ` pr-tracker-bot
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-07-08  0:14 Stephen Boyd
2021-07-08 19:49 ` 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=aj1NUYRrD30ctAbt@redhat.com \
    --to=bmasney@redhat.com \
    --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