linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	"David S. Miller" <davem@davemloft.net>,
	Marcel Holtmann <marcel@holtmann.org>,
	Simon Horman <simon.horman@netronome.com>,
	Harish Bandi <c-hbandi@codeaurora.org>,
	Venkata Lakshmi Narayana Gubba <gubbaven@codeaurora.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	Rocky Liao <rjliao@codeaurora.org>,
	Matthias Brugger <mbrugger@suse.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	netdev <netdev@vger.kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] docs: dt: fix a broken reference for a file converted to json
Date: Fri, 27 Mar 2020 15:54:56 +0100	[thread overview]
Message-ID: <20200327155456.6d582bde@coco.lan> (raw)
In-Reply-To: <CAL_JsqLZQN253PDi-HXtP3s5CCg0OzaUK99onC9UjQWeVw3KYw@mail.gmail.com>

Em Fri, 27 Mar 2020 08:26:58 -0600
Rob Herring <robh+dt@kernel.org> escreveu:

> On Fri, Mar 27, 2020 at 7:34 AM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> > Changeset 32ced09d7903 ("dt-bindings: serial: Convert slave-device bindings to json-schema")
> > moved a binding to json and updated the links. Yet, one link
> > was forgotten.  
> 
> It was not. There's a merge conflict, so I dropped it until after rc1.

Ah, ok.

Thanks!
Mauro

> >
> > Update this one too.
> >
> > Fixes: 32ced09d7903 ("dt-bindings: serial: Convert slave-device bindings to json-schema")
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > ---
> >  Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
> > index beca6466d59a..d2202791c1d4 100644
> > --- a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
> > +++ b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
> > @@ -29,7 +29,7 @@ Required properties for compatible string qcom,wcn399x-bt:
> >
> >  Optional properties for compatible string qcom,wcn399x-bt:
> >
> > - - max-speed: see Documentation/devicetree/bindings/serial/slave-device.txt
> > + - max-speed: see Documentation/devicetree/bindings/serial/serial.yaml
> >   - firmware-name: specify the name of nvm firmware to load
> >   - clocks: clock provided to the controller
> >
> > --
> > 2.25.1
> >  



Thanks,
Mauro

      reply	other threads:[~2020-03-27 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 13:34 [PATCH] docs: dt: fix a broken reference for a file converted to json Mauro Carvalho Chehab
2020-03-27 14:26 ` Rob Herring
2020-03-27 14:54   ` Mauro Carvalho Chehab [this message]

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=20200327155456.6d582bde@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=c-hbandi@codeaurora.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gubbaven@codeaurora.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mbrugger@suse.com \
    --cc=mka@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=rjliao@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=simon.horman@netronome.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).