From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL 1/4] Devicetree binding changes for omaps for v6.6
Date: Thu, 10 Aug 2023 12:16:50 +0300 [thread overview]
Message-ID: <pull-1691658952-110529@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v6.6/dt-bindings-signed
for you to fetch changes up to c5a5583ecfa02a858983a0cad710201fe0eea03f:
dt-bindings: omap: Partially convert omap.txt to yaml (2023-07-31 09:09:21 +0300)
----------------------------------------------------------------
Devicetree binding changes for omaps for v6.6
Just one change to get started on SoC yaml binding changes for omaps.
----------------------------------------------------------------
Andrew Davis (1):
dt-bindings: omap: Partially convert omap.txt to yaml
.../devicetree/bindings/arm/omap/omap.txt | 99 ------------
Documentation/devicetree/bindings/arm/ti/omap.yaml | 176 +++++++++++++++++++++
2 files changed, 176 insertions(+), 99 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/ti/omap.yaml
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-08-10 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 9:16 Tony Lindgren [this message]
2023-08-10 9:16 ` [GIT PULL 2/4] Maintainer file list update for omaps for v6.6 Tony Lindgren
2023-08-10 9:16 ` [GIT PULL 3/4] Devicetree changes " Tony Lindgren
2023-08-10 9:16 ` [GIT PULL 4/4] SoC " Tony Lindgren
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=pull-1691658952-110529@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@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 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).