mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@suse.de>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: Maxime Ripard <maxime@cerno.tech>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] clk: bcm: rpi: Add support for two more clocks
Date: Fri, 15 Apr 2022 10:48:39 +0300	[thread overview]
Message-ID: <20220415074839.5ma5n57rmhv7tk4s@suse> (raw)
In-Reply-To: <20220405090431.ktlybn62eueh7gqi@houat>

Hi Michael, Stephen,

On 04-05 11:04, Maxime Ripard wrote:
> Date: Tue, 5 Apr 2022 11:04:31 +0200
> From: Maxime Ripard <maxime@cerno.tech>
> To: "Ivan T. Ivanov" <iivanov@suse.de>
> Cc: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd
>  <sboyd@kernel.org>, linux-clk@vger.kernel.org,
>  linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2 0/2] clk: bcm: rpi: Add support for two more clocks
> Message-ID: <20220405090431.ktlybn62eueh7gqi@houat>
Tags: all clk linux me ring
> 
> On Tue, Apr 05, 2022 at 11:25:01AM +0300, Ivan T. Ivanov wrote:
> > Add missing clock required by RPiVid video decoder and make HDMI
> > pixel clock more reliable.
> 
> For both patches:
> Acked-by: Maxime Ripard <maxime@cerno.tech>
> 

Any chance that this is merged in foreseeable future?
Do you have any comments or objections?

Thanks,
Ivan



  reply	other threads:[~2022-04-15  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05  8:25 Ivan T. Ivanov
2022-04-05  8:25 ` [PATCH v2 1/2] clk: bcm: rpi: Add support HEVC clock Ivan T. Ivanov
2022-04-05  8:25 ` [PATCH v2 2/2] clk: bcm: rpi: Handle pixel clock in firmware Ivan T. Ivanov
2022-04-05 11:21   ` Dave Stevenson
2022-04-05  9:04 ` [PATCH v2 0/2] clk: bcm: rpi: Add support for two more clocks Maxime Ripard
2022-04-15  7:48   ` Ivan T. Ivanov [this message]
2022-04-15  8:38     ` Stefan Wahren

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=20220415074839.5ma5n57rmhv7tk4s@suse \
    --to=iivanov@suse.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=stefan.wahren@i2se.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
all inboxes | Powered by JetHome®