Re: [PATCH v2 00/21] Refine memblock API

On Thu, Sep 26, 2019 at 11:04 AM Mike Rapoport wrote: > > Hi, > > On Thu, Sep 26, 2019 at 08:09:52AM -0500, Adam Ford wrote: > > On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam wrote: > > > > > > On Wed, Sep 25, 2019 at 9:17 AM Adam Ford wrote: > > > > > > > I tried cma=256M and noticed the cma d

Re: [PATCH v2 00/21] Refine memblock API

Hi, On Thu, Sep 26, 2019 at 08:09:52AM -0500, Adam Ford wrote: > On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam wrote: > > > > On Wed, Sep 25, 2019 at 9:17 AM Adam Ford wrote: > > > > > I tried cma=256M and noticed the cma dump at the beginning didn't > > > change. Do we need to setup a reserve

Re: [PATCH v2 00/21] Refine memblock API

On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam wrote: > > On Wed, Sep 25, 2019 at 9:17 AM Adam Ford wrote: > > > I tried cma=256M and noticed the cma dump at the beginning didn't > > change. Do we need to setup a reserved-memory node like > > imx6ul-ccimx6ulsom.dtsi did? > > I don't think so. >

Re: [PATCH 0/7] add support for clocksource/clockevent DT selection

On 25.09.2019 20:19, Daniel Lezcano wrote: > External E-Mail > > > Hi Claudiu, > > On 10/09/2019 15:47, Claudiu Beznea wrote: >> Hi, >> >> This series adds support to permit the selection of clocksource/clockevent >> via DT. > > Thanks for the proposal and taking care of making some progress