mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: Barebox Mailing List <barebox@lists.infradead.org>
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [PATCH 2/3] Documentation: state: fix closing brace without opening brace
Date: Mon, 10 Dec 2018 16:55:10 +0100	[thread overview]
Message-ID: <20181210155511.1376-2-rhi@pengutronix.de> (raw)
In-Reply-To: <20181210155511.1376-1-rhi@pengutronix.de>

Also fix the resulting sphinx warning:

  Documentation/user/state.rst:650: WARNING: Explicit markup ends without a blank line; unexpected unindent.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 Documentation/user/state.rst | 1 -
 1 file changed, 1 deletion(-)

diff --git a/Documentation/user/state.rst b/Documentation/user/state.rst
index 89129add77..07743df0cb 100644
--- a/Documentation/user/state.rst
+++ b/Documentation/user/state.rst
@@ -636,29 +636,28 @@ within the EEPROM.
 
 .. code-block:: text
 
 	eeprom@50 {
 		partitions {
 			compatible = "fixed-partitions";
 			#size-cells = <1>;
 			#address-cells = <1>;
 			backend_state_eeprom: eeprom_state_memory@400 {
 				reg = <0x400 0x100>;
 				label = "state-eeprom";
 			};
 		};
 	};
-};
 
 With this 'backend' definition it's possible to define the *state* variable set
 content, its backend-type and *state* variable layout.
 
 .. code-block:: text
 
 	aliases {
 		state = &state_eeprom;
 	};
 
 	state_eeprom: eeprom_memory {
 		#address-cells = <1>;
 		#size-cells = <1>;
 		compatible = "barebox,state";
-- 
2.19.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-12-10 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 15:55 [PATCH 1/3] Documentation: i.MX: improve wording, add markup and missing articles Roland Hieber
2018-12-10 15:55 ` Roland Hieber [this message]
2018-12-10 15:55 ` [PATCH 3/3] Documentation: i.MX: Kindle 4/5: fix sphinx warnings Roland Hieber
2018-12-13  6:57 ` [PATCH 1/3] Documentation: i.MX: improve wording, add markup and missing articles Sascha Hauer
2018-12-14 10:13   ` Roland Hieber
2018-12-17  9:45     ` Sascha Hauer
2019-01-11 11:35       ` Roland Hieber
2019-01-16 10:15         ` [RESEND] [PATCH 0/2] small doc fixes Roland Hieber
2019-01-16 10:16           ` [RESEND] [PATCH 1/2] Documentation: state: fix closing brace without opening brace Roland Hieber
2019-01-16 10:16           ` [RESEND] [PATCH 2/2] Documentation: i.MX: Kindle 4/5: fix sphinx warnings Roland Hieber
2019-01-17  7:39           ` [RESEND] [PATCH 0/2] small doc fixes Sascha Hauer

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=20181210155511.1376-2-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=barebox@lists.infradead.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