From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Devicetree vendor prefix schema for 5.2
Date: Thu, 16 May 2019 15:43:27 -0500 [thread overview]
Message-ID: <CAL_JsqLtkGfSX5bdRWy7MXM+opAd-gWzhTorUoVXOpKktN8YKQ@mail.gmail.com> (raw)
Linus,
Please pull this 1 additional commit for rc1. This had to wait for all
the merge window changes to vendor-prefixes.txt to go in to regenerate
it.
Rob
The following changes since commit 01be377c62210a8d8fef35be906f9349591bb7cd:
Merge tag 'media/v5.2-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
(2019-05-16 11:57:16 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
tags/devicetree-for-5.2-part2
for you to fetch changes up to 8122de54602e30f0a73228ab6459a3654e652b92:
dt-bindings: Convert vendor prefixes to json-schema (2019-05-16
15:27:21 -0500)
----------------------------------------------------------------
Conversion of vendor-prefixes.txt to json-schema
----------------------------------------------------------------
Rob Herring (1):
dt-bindings: Convert vendor prefixes to json-schema
.../devicetree/bindings/vendor-prefixes.txt | 476 ----------
.../devicetree/bindings/vendor-prefixes.yaml | 977 +++++++++++++++++++++
2 files changed, 977 insertions(+), 476 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/vendor-prefixes.txt
create mode 100644 Documentation/devicetree/bindings/vendor-prefixes.yaml
next reply other threads:[~2019-05-16 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 20:43 Rob Herring [this message]
2019-05-17 2:25 ` [GIT PULL] Devicetree vendor prefix schema for 5.2 pr-tracker-bot
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=CAL_JsqLtkGfSX5bdRWy7MXM+opAd-gWzhTorUoVXOpKktN8YKQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).