All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: Stephen Boyd <sboyd@kernel.org>, Benoit Parrot <bparrot@ti.com>,
	linux-clk@vger.kernel.org, linux-omap@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch v5 1/3] clk: ti: dra7: add vpe clkctrl data
Date: Thu, 23 Jan 2020 09:22:45 -0800	[thread overview]
Message-ID: <20200123172245.GD5885@atomide.com> (raw)
In-Reply-To: <33a9848a-04c4-6545-f477-d6510faceb51@ti.com>

* Tero Kristo <t-kristo@ti.com> [200121 07:33]:
> On 30/12/2019 21:58, Stephen Boyd wrote:
> > Quoting Benoit Parrot (2019-12-11 06:08:08)
> > > Add clkctrl data for VPE.
> > > 
> > > Signed-off-by: Benoit Parrot <bparrot@ti.com>
> > > Acked-by: Tony Lindgren <tony@atomide.com>
> > > Acked-by: Rob Herring <robh@kernel.org>
> > > ---
> > 
> > Acked-by: Stephen Boyd <sboyd@kernel.org>
> > 
> 
> Queued this patch towards 5.6, thanks.

And I'm picking the dts changes into
omap-for-v5.6/ti-sysc-dt-cam.

Thanks,

Tony

  reply	other threads:[~2020-01-23 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 14:08 [Patch v5 0/3] ARM: dts: dra7: add vpe nodes Benoit Parrot
2019-12-11 14:08 ` Benoit Parrot
2019-12-11 14:08 ` [Patch v5 1/3] clk: ti: dra7: add vpe clkctrl data Benoit Parrot
2019-12-11 14:08   ` Benoit Parrot
2019-12-30 19:58   ` Stephen Boyd
2019-12-30 19:58     ` Stephen Boyd
2020-01-21  7:32     ` Tero Kristo
2020-01-21  7:32       ` Tero Kristo
2020-01-23 17:22       ` Tony Lindgren [this message]
2019-12-11 14:08 ` [Patch v5 2/3] ARM: dts: dra7: add vpe clkctrl node Benoit Parrot
2019-12-11 14:08   ` Benoit Parrot
2019-12-11 14:08 ` [Patch v5 3/3] ARM: dts: dra7: Add ti-sysc node for VPE Benoit Parrot
2019-12-11 14:08   ` Benoit Parrot

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=20200123172245.GD5885@atomide.com \
    --to=tony@atomide.com \
    --cc=bparrot@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=t-kristo@ti.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 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.