All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	<david@gibson.dropbear.id.au>, <sjg@chromium.org>
Cc: <devicetree@vger.kernel.org>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	<linux-kernel@vger.kernel.org>, <linux-kbuild@vger.kernel.org>,
	<devicetree-compiler@vger.kernel.org>,
	Ian Lepore <ian@freebsd.org>
Subject: [RFC PATCH v2 3/4] ARM: dts: stm32: Add dtb build information entry for stm32mp157c-dk2
Date: Fri, 21 Feb 2020 17:14:17 +0100	[thread overview]
Message-ID: <20200221161418.20225-4-alexandre.torgue@st.com> (raw)
In-Reply-To: <20200221161418.20225-1-alexandre.torgue@st.com>

dtb-build.txt is a file containing device tree build information (date,
source version ...). This file is used to fill "build-info" entry which
will be displayed during kernel boot.

Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>

diff --git a/arch/arm/boot/dts/stm32mp157c-dk2.dts b/arch/arm/boot/dts/stm32mp157c-dk2.dts
index 7985b80967ca..387d3bcf5fa3 100644
--- a/arch/arm/boot/dts/stm32mp157c-dk2.dts
+++ b/arch/arm/boot/dts/stm32mp157c-dk2.dts
@@ -15,6 +15,7 @@
 / {
 	model = "STMicroelectronics STM32MP157C-DK2 Discovery Board";
 	compatible = "st,stm32mp157c-dk2", "st,stm32mp157";
+	build-info = /incbin/("dtb-build.txt");
 
 	aliases {
 		ethernet0 = &ethernet0;
-- 
2.17.1


WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Torgue <alexandre.torgue@st.com>
To: robh+dt@kernel.org, Frank Rowand <frowand.list@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	david@gibson.dropbear.id.au, sjg@chromium.org
Cc: devicetree@vger.kernel.org,
	Alexandre Torgue <alexandre.torgue@st.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	devicetree-compiler@vger.kernel.org, Ian Lepore <ian@freebsd.org>
Subject: [RFC PATCH v2 3/4] ARM: dts: stm32: Add dtb build information entry for stm32mp157c-dk2
Date: Fri, 21 Feb 2020 17:14:17 +0100	[thread overview]
Message-ID: <20200221161418.20225-4-alexandre.torgue@st.com> (raw)
In-Reply-To: <20200221161418.20225-1-alexandre.torgue@st.com>

dtb-build.txt is a file containing device tree build information (date,
source version ...). This file is used to fill "build-info" entry which
will be displayed during kernel boot.

Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>

diff --git a/arch/arm/boot/dts/stm32mp157c-dk2.dts b/arch/arm/boot/dts/stm32mp157c-dk2.dts
index 7985b80967ca..387d3bcf5fa3 100644
--- a/arch/arm/boot/dts/stm32mp157c-dk2.dts
+++ b/arch/arm/boot/dts/stm32mp157c-dk2.dts
@@ -15,6 +15,7 @@
 / {
 	model = "STMicroelectronics STM32MP157C-DK2 Discovery Board";
 	compatible = "st,stm32mp157c-dk2", "st,stm32mp157";
+	build-info = /incbin/("dtb-build.txt");
 
 	aliases {
 		ethernet0 = &ethernet0;
-- 
2.17.1

  parent reply	other threads:[~2020-02-21 16:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 16:14 [RFC PATCH v2 0/4] Add device tree build information Alexandre Torgue
2020-02-21 16:14 ` Alexandre Torgue
2020-02-21 16:14 ` [RFC PATCH v2 1/4] scripts: Add script to generate dtb " Alexandre Torgue
2020-02-21 16:14   ` Alexandre Torgue
2020-02-21 16:14   ` Alexandre Torgue
2020-02-21 17:52   ` Frank Rowand
2020-02-21 17:52     ` Frank Rowand
2020-02-21 19:38     ` Rob Herring
2020-02-21 19:38       ` Rob Herring
2020-03-02 12:40       ` Alexandre Torgue
2020-03-02 12:40         ` Alexandre Torgue
2020-02-23 21:59     ` David Gibson
2020-02-23 21:59       ` David Gibson
2020-02-24  0:57       ` Frank Rowand
2020-02-21 16:14 ` [RFC PATCH v2 2/4] of: fdt: print " Alexandre Torgue
2020-02-21 16:14   ` Alexandre Torgue
2020-02-21 16:14   ` Alexandre Torgue
2020-02-26 21:36   ` Rob Herring
2020-02-26 21:36     ` Rob Herring
2020-02-21 16:14 ` Alexandre Torgue [this message]
2020-02-21 16:14   ` [RFC PATCH v2 3/4] ARM: dts: stm32: Add dtb build information entry for stm32mp157c-dk2 Alexandre Torgue
2020-02-21 16:14 ` [RFC PATCH v2 4/4] script: make automatic dtb build info generation Alexandre Torgue
2020-02-21 16:14   ` Alexandre Torgue
2020-02-21 16:14   ` Alexandre Torgue
2020-02-21 17:59   ` Frank Rowand
2020-02-26 20:56   ` Rob Herring
2020-02-21 17:47 ` [RFC PATCH v2 0/4] Add device tree build information Frank Rowand
2020-02-21 17:47   ` Frank Rowand
2020-02-28 17:47   ` Frank Rowand
2020-03-02 12:55     ` Alexandre Torgue
2020-03-02 12:55       ` Alexandre Torgue
2020-03-31  1:03       ` Steve McIntyre
2020-03-31  1:03         ` Steve McIntyre
2020-03-31 15:00         ` Alexandre Torgue
2020-03-31 15:00           ` Alexandre Torgue
  -- strict thread matches above, loose matches on Subject: below --
2020-02-21 16:12 [RFC PATCH v2 0/4] Alexandre Torgue
2020-02-21 16:12 ` [RFC PATCH v2 3/4] ARM: dts: stm32: Add dtb build information entry for stm32mp157c-dk2 Alexandre Torgue
2020-02-21 16:12   ` Alexandre Torgue

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=20200221161418.20225-4-alexandre.torgue@st.com \
    --to=alexandre.torgue@st.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=ian@freebsd.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=robh+dt@kernel.org \
    --cc=sjg@chromium.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.