From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Wolfgang Grandegger <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>,
<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 04/12] docs: dt: fix references to m_can.txt file
Date: Tue, 17 Mar 2020 15:06:09 +0100 [thread overview]
Message-ID: <20200317150609.4d5c7c71@coco.lan> (raw)
In-Reply-To: <60f77c6f-0536-1f50-1b49-2f604026a5cb@ti.com>
Em Tue, 17 Mar 2020 08:29:45 -0500
Dan Murphy <dmurphy@ti.com> escreveu:
> Hello
>
> On 3/17/20 8:17 AM, Marc Kleine-Budde wrote:
> > On 3/17/20 2:10 PM, Mauro Carvalho Chehab wrote:
> >> This file was converted to json and renamed. Update its
> >> references accordingly.
> >>
> >> Fixes: 824674b59f72 ("dt-bindings: net: can: Convert M_CAN to json-schema")
>
> I am trying to find out where the above commit was applied
>
> I don't see it in can-next or linux-can. I need to update the tcan dt
> binding file as it was missed.
>
> And I am not sure why the maintainers of these files were not CC'd on
> the conversion of this binding.
From Next/merge.log:
Merging devicetree/for-next (d047cd8a2760 scripts/dtc: Update to upstream version v1.6.0-2-g87a656ae5ff9)
$ git merge devicetree/for-next
Removing scripts/dtc/libfdt/Makefile.libfdt
Removing scripts/dtc/Makefile.dtc
...
create mode 100644 Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
delete mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt
It sounds that those came from DT for-next branch.
Thanks,
Mauro
next prev parent reply other threads:[~2020-03-17 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1584450500.git.mchehab+huawei@kernel.org>
2020-03-17 13:10 ` [PATCH 04/12] docs: dt: fix references to m_can.txt file Mauro Carvalho Chehab
2020-03-17 13:17 ` Marc Kleine-Budde
2020-03-17 13:29 ` Dan Murphy
2020-03-17 13:54 ` Benjamin GAIGNARD
2020-03-17 14:06 ` Mauro Carvalho Chehab [this message]
2020-03-30 21:05 ` Rob Herring
2020-03-17 13:10 ` [PATCH 05/12] docs: dt: fix references to ap806-system-controller.txt Mauro Carvalho Chehab
2020-03-17 13:50 ` Bartosz Golaszewski
2020-03-17 16:12 ` Miquel Raynal
2020-03-30 21:06 ` Rob Herring
2020-03-17 13:10 ` [PATCH 06/12] docs: dt: fix a broken reference to input.yaml Mauro Carvalho Chehab
2020-03-30 21:07 ` Rob Herring
2020-03-17 13:10 ` [PATCH 07/12] docs: dt: fix broken reference to phy-cadence-torrent.yaml Mauro Carvalho Chehab
2020-03-30 21:09 ` Rob Herring
2020-03-17 13:10 ` [PATCH 10/12] docs: dt: display/ti: fix typos at the devicetree/ directory name Mauro Carvalho Chehab
2020-03-17 13:37 ` Jyri Sarha
2020-03-30 21:15 ` Rob Herring
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=20200317150609.4d5c7c71@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=benjamin.gaignard@st.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.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).