From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: fix broken doc refs due to yaml conversion
Date: Tue, 13 Oct 2020 10:52:39 +0200 [thread overview]
Message-ID: <20201013105239.348efc0c@coco.lan> (raw)
In-Reply-To: <20201012192114.GA1938842@bogus>
Em Mon, 12 Oct 2020 14:21:14 -0500
Rob Herring <robh@kernel.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@kernel.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
next prev parent reply other threads:[~2020-10-13 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 12:15 [PATCH 0/2] Fix new warnings at linux-next Mauro Carvalho Chehab
2020-10-09 12:15 ` Mauro Carvalho Chehab
2020-10-09 12:15 ` [PATCH 1/2] MAINTAINERS: fix broken doc refs due to yaml conversion Mauro Carvalho Chehab
2020-10-12 19:21 ` Rob Herring
2020-10-13 8:52 ` Mauro Carvalho Chehab [this message]
2020-10-21 10:00 ` Mauro Carvalho Chehab
2020-10-12 19:26 ` Stephen Boyd
2020-10-09 12:15 ` [PATCH 2/2] crypto: sun8x-ce*: update entries to its documentation Mauro Carvalho Chehab
2020-10-09 12:15 ` Mauro Carvalho Chehab
2020-10-09 18:39 ` Corentin Labbe
2020-10-09 18:39 ` Corentin Labbe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201013105239.348efc0c@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jerome.pouiller@silabs.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.