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,
Mark Brown <broonie@kernel.org>
Subject: Re: [GIT PULL] clk changes for the merge window
Date: Thu, 23 Apr 2026 06:21:24 -0400 [thread overview]
Message-ID: <aenypBUNgqrr9nCE@redhat.com> (raw)
In-Reply-To: <aeeHSrZmAqE4ugXY@redhat.com>
Hi Stephen,
On Tue, Apr 21, 2026 at 10:18:50AM -0400, Brian Masney wrote:
> Here's some additional patch sets that were posted this development
> cycle that I feel are ready. I don't see any objections from the
> community, and some such as the Mobileye series, looked like they
> were going to be picked up during this development cycle.
>
> - Feb 18 - Felix Gu <ustc.gu@gmail.com>
> [PATCH] clk: aspeed: ast2700: Add missing NULL pointer check for devm_kasprintf()
> https://lore.kernel.org/linux-clk/20260218-ast2700-v1-1-2388e0fe3597@gmail.com/
>
> - Feb 24 - Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> [PATCH v2 0/3] clk: x86: lpss-atom: A couple of cleanups and a feature
> https://lore.kernel.org/linux-clk/20260224121159.3503754-1-andriy.shevchenko@linux.intel.com/
>
> - Feb 24 - Shawn Guo <shawnguo@kernel.org>
> [PATCH] clk: hisilicon: reset: Use kzalloc instead of kmalloc
> https://lore.kernel.org/linux-clk/20260224021912.54365-1-shawnguo@kernel.org/
>
> - Mar 3 - "J. Neuschäfer via B4 Relay" <devnull+j.ne.posteo.net@kernel.org>
> [PATCH v2] clk: hisilicon: Improve deallocation in error path
> https://lore.kernel.org/linux-clk/20260303-hisi-error-v2-1-7cd9b43d8fbb@posteo.net/
>
> - Mar 12 - Peng Fan <peng.fan@oss.nxp.com>
> [PATCH v9 0/6] clk: Support spread spectrum and use it in clk-scmi
> https://lore.kernel.org/linux-clk/20260312-clk-ssc-v7-1-v9-0-0a9d2e188d9e@nxp.com/
>
> - Mar 25 - Rosen Penev <rosenp@gmail.com>
> [PATCH] clk: visconti: pll: use kzalloc_flex
> https://lore.kernel.org/linux-clk/20260326042317.122536-1-rosenp@gmail.com/
>
> - Mar 25 - Rosen Penev <rosenp@gmail.com>
> [PATCH] clk: bcm: iproc-asiu: simplify allocation
> https://lore.kernel.org/linux-clk/20260326045324.240150-1-rosenp@gmail.com/
>
> - Mar 25 - Rosen Penev <rosenp@gmail.com>
> [PATCH] clk: clk-max77686: kzalloc + kcalloc to kzalloc
> https://lore.kernel.org/linux-clk/20260326052847.335089-1-rosenp@gmail.com/
>
> - Mar 25 - Benoît Monin <benoit.monin@bootlin.com>
> Mobileye EyeQ7H
> This message lists the merge strategy for 3 different patch sets.
> https://lore.kernel.org/linux-clk/2786053.vuYhMxLoTh@benoit.monin/
>
> - Mar 31 - Rosen Penev <rosenp@gmail.com>
> [PATCHv3] clk: hisilicon: clkdivider-hi6220: use kzalloc_flex
> https://lore.kernel.org/linux-clk/20260401023551.27978-1-rosenp@gmail.com/
>
> - Apr 3 - Rosen Penev <rosenp@gmail.com>
> [PATCHv2] clk: mvebu: use kzalloc_flex
> https://lore.kernel.org/linux-clk/20260403194701.11902-1-rosenp@gmail.com/
>
> - Apr 7 - Johan Hovold <johan@kernel.org>
> [PATCH] clk: rk808: fix OF node reference imbalance
> https://lore.kernel.org/linux-clk/20260407095027.2625516-1-johan@kernel.org/
>
> I know it's getting late in the merge window, but if possible, it would
> be nice to get these in via a second pull.
>
> I don't want to hold up this pull since everything there looks fine.
Mark Brown reported a boot regression on March 31st on the on Raspberry
Pi 3B+ in this thread that's now in mainline:
https://lore.kernel.org/linux-clk/18719902-4b4f-4766-ba92-658f3576f68b@sirena.org.uk/
The corresponding fix was quickly provided the next day:
https://lore.kernel.org/all/20260401111416.562279-2-mcanal@igalia.com/
Could you also get this in?
Thanks,
Brian
next prev parent reply other threads:[~2026-04-23 10:21 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 18:32 [GIT PULL] clk changes for the merge window Stephen Boyd
2026-04-21 14:18 ` Brian Masney
2026-04-23 10:21 ` Brian Masney [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=aenypBUNgqrr9nCE@redhat.com \
--to=bmasney@redhat.com \
--cc=broonie@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 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.