From: Brian Masney <bmasney@redhat.com>
To: "Benoît Monin" <benoit.monin@bootlin.com>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clk: eyeq: Support for Mobileye EyeQ7H
Date: Fri, 17 Jul 2026 08:45:00 -0400 [thread overview]
Message-ID: <CABx5tqL06iPpfLzP2W5YcipmgJRc08Db8=dDRoVOWyVAG+Ww0A@mail.gmail.com> (raw)
In-Reply-To: <dUZ-Y63mToq5Uy17STAyZw@bootlin.com>
Hi Benoît,
On Fri, Jul 17, 2026 at 4:26 AM Benoît Monin <benoit.monin@bootlin.com> wrote:
> On Wednesday, 17 June 2026 at 11:25:03 CEST, Benoît Monin wrote:
> > Here is a pull for the clk-eyeq driver adding support for Mobileye EyeQ7H
> > SoC. It has been posted as a patch series previously, this pull request is
> > identical to the latest version posted[1].
> >
> > Alongside the changes to the clk-eyeq driver, this pull request also
> > provides the dt-bindings reviewed by Krzysztof Kozlowski, a change to the
> > reset-eyeq driver acked by Philipp Zabel and a small rework of the
> > fixed-factor clocks reviewed by Brian Masney.
> >
> > [1]: https://patch.msgid.link/20260604-clk-eyeq7-v8-0-53f618174cf6@bootlin.com
> >
> >
> > The following changes since commit 5d6919055dec134de3c40167a490f33c74c12581:
> >
> > Linux 7.1-rc3 (2026-05-10 14:08:09 -0700)
> >
> > are available in the Git repository at:
> >
> > https://github.com/benoitmonin/linux tags/clk-eyeq7h-7.2
> >
> > for you to fetch changes up to fc58615596c5bd701d868813ac595489f3939d83:
> >
> > clk: eyeq: Add EyeQ7H compatibles (2026-06-15 17:42:32 +0200)
> >
> So, this did not make the cut for 7.2... I am wondering what I should do.
>
> Should I rebase on v7.2-rc1 and post the series again?
>
> I would really like to see this series merged at some point.
If the series still applies cleanly, then I recommend sending a second
GIT PULL based on 7.2-rc1.
If not, post a new rebased version, then around rc6 post a pull as well.
Brian
prev parent reply other threads:[~2026-07-17 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 9:25 Benoît Monin
2026-06-17 10:51 ` Brian Masney
2026-06-17 13:04 ` Benoît Monin
2026-06-17 13:23 ` Brian Masney
2026-07-17 8:26 ` Benoît Monin
2026-07-17 12:45 ` 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='CABx5tqL06iPpfLzP2W5YcipmgJRc08Db8=dDRoVOWyVAG+Ww0A@mail.gmail.com' \
--to=bmasney@redhat.com \
--cc=benoit.monin@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.com \
/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