Linux clock framework development
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clk: various improvements and fixes
Date: Mon, 29 Jun 2026 18:38:32 -0400	[thread overview]
Message-ID: <akLz6H3ZoN2cCYQN@redhat.com> (raw)
In-Reply-To: <akLzCVzbMbUsgDda@redhat.com>

On Mon, Jun 29, 2026 at 06:34:49PM -0400, Brian Masney wrote:
> Hi Stephen,
> 
> Here's various improvements and fixes that weren't picked up during the
> last merge window that I feel are ready. Let me know if you'd like me to
> drop anything and I can send you a v2. Details from the 19 contributors are
> below in the signed tag.

I forgot to mention that I didn't include Benoît's support for the Mobileye
EyeQ7H SoC since he already has a separate pull ready:

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

Brian


      reply	other threads:[~2026-06-29 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 22:34 [GIT PULL] clk: various improvements and fixes Brian Masney
2026-06-29 22:38 ` Brian Masney [this message]

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=akLz6H3ZoN2cCYQN@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 \
    /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