[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJ3VG7Yr6OqKTZD16TowOksNTQkO859UNLFdyMSnS3VQQ@mail.gmail.com>
Date: Mon, 10 Sep 2018 08:51:25 -0500
From: Rob Herring <robh@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-riscv@...ts.infradead.org,
Palmer Dabbelt <palmer@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>
Subject: Re: [PATCH 14/21] riscv: use for_each_of_cpu_node iterator
On Mon, Sep 10, 2018 at 8:38 AM Christoph Hellwig <hch@...radead.org> wrote:
>
> On Wed, Sep 05, 2018 at 02:37:31PM -0500, Rob Herring wrote:
> > Use the for_each_of_cpu_node iterator to iterate over cpu nodes. This
> > has the side effect of defaulting to iterating using "cpu" node names in
> > preference to the deprecated (for FDT) device_type == "cpu".
> >
> > Cc: Palmer Dabbelt <palmer@...ive.com>
> > Cc: Albert Ou <aou@...s.berkeley.edu>
> > Cc: linux-riscv@...ts.infradead.org
> > Signed-off-by: Rob Herring <robh@...nel.org>
> > ---
> > Please ack and I will take via the DT tree. This is dependent on the
> > first 2 patches.
>
> We have a few pending patches in this area that look like they might
> conflict. It might be worth to delay this one and apply it post -rc1
> to avoid dependencies if that isn't a problem for you.
Sure. That's fine.
Rob
Powered by blists - more mailing lists