[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190608075113.32f2c7bb@coco.lan>
Date: Sat, 8 Jun 2019 07:51:13 -0300
From: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Hugues Fruchet <hugues.fruchet@...com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>,
Olivier Moysan <olivier.moysan@...com>,
Arnaud Pouliquen <arnaud.pouliquen@...com>,
Liam Girdwood <lgirdwood@...il.com>,
devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, alsa-devel@...a-project.org
Subject: Re: [PATCH v3 17/20] dt: bindings: fix some broken links from
txt->yaml conversion
Em Fri, 7 Jun 2019 19:57:28 +0100
Mark Brown <broonie@...nel.org> escreveu:
> On Fri, Jun 07, 2019 at 03:54:33PM -0300, Mauro Carvalho Chehab wrote:
> > Some new files got converted to yaml, but references weren't
> > updated accordingly.
>
> These should probably just be sent as normal patches rather than tied in
> with the rest of this series...
Thanks for applying it!
Yeah, but the problem with documentation patches is that sometimes
the patches are merged via docs tree, and sometimes via maintainer's
tree, depending on the subsystem.
Anyway, Jon merged this week a patch that should produce warnings
on COMPILE_TEST builds when a file has a broken link.
Hopefully, this will help a lot to warn people against regressions
related to it.
Thanks,
Mauro
Powered by blists - more mailing lists