[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201013105239.348efc0c@coco.lan>
Date: Tue, 13 Oct 2020 10:52:39 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Rob Herring <robh@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
Jérôme Pouiller <jerome.pouiller@...abs.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>, devel@...verdev.osuosl.org,
devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: fix broken doc refs due to yaml
conversion
Em Mon, 12 Oct 2020 14:21:14 -0500
Rob Herring <robh@...nel.org> escreveu:
> On Fri, Oct 09, 2020 at 02:15:30PM +0200, Mauro Carvalho Chehab wrote:
> > Several *.txt files got converted to yaml. Update their
> > references at MAINTAINERS file accordingly.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> > ---
> > Documentation/devicetree/bindings/clock/hi6220-clock.txt | 2 +-
> > MAINTAINERS | 9 ++++-----
> > .../devicetree/bindings/net/wireless/silabs,wfx.yaml | 2 +-
> > 3 files changed, 6 insertions(+), 7 deletions(-)
>
> Doesn't apply for me.
It is based on the top of -next, so perhaps it depends on some other
changes that aren't upstream yet and comes from other trees.
I could try to split it, but I guess the easiest way is
to just push this one by the end of the merge window, together
with the remaining patches I have left, fixing the other doc
build issues.
Would that work for you?
Thanks,
Mauro
Powered by blists - more mailing lists