[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <153577001451.19113.16924655760277630355@swboyd.mtv.corp.google.com>
Date: Fri, 31 Aug 2018 19:46:54 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Eddie James <eajames@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Cc: linux-media@...r.kernel.org, linux-aspeed@...ts.ozlabs.org,
openbmc@...ts.ozlabs.org, andrew@...id.au, mchehab@...nel.org,
joel@....id.au, robh+dt@...nel.org, mark.rutland@....com,
devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
mturquette@...libre.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/4] media: platform: Add Aspeed Video Engine driver
Quoting Eddie James (2018-08-31 12:30:02)
>
>
> On 08/31/2018 12:56 PM, Stephen Boyd wrote:
> > Quoting Eddie James (2018-08-29 14:09:29)
> > Please let me know your merge strategy here. I can ack the clk patches
> > because they look fine from high-level clk driver perspective (maybe
> > Joel can take a closer look) or I can merge the patches into clk-next
> > and get them into next release while the video driver gets reviewed.
>
> Thanks for taking a look! Probably preferable to get the clk patches
> into clk-next first (though Joel reviewing would be great). I just put
> everything in the same set for the sake of explaining the necessity of
> the clk changes.
>
Ok. If Joel is able to review then I can easily merge it into clk-next.
Powered by blists - more mailing lists