From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] global_data: Remove comment of reserved arch-specific GD flags
Date: Fri, 16 Aug 2019 14:45:29 +0200 [thread overview]
Message-ID: <20190816124529.1178-2-sr@denx.de> (raw)
In-Reply-To: <20190816124529.1178-1-sr@denx.de>
With the removal of the x86 specific GD flags, there are no arch-
specific GD flags any more. Let's remove the comment about reserving the
upper 16 bits for arch-specific flags in the common header. This gives
us more flexibility with the usage of the GD flags.
As a matter of fact, we are already using more than 16 bits for common
GD flags (with the addition of GD_FLG_WDT_READY).
Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Bin Meng <bmeng.cn@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>
Cc: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
---
include/asm-generic/global_data.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/asm-generic/global_data.h b/include/asm-generic/global_data.h
index 5372d5d8cd..7587ba2ee5 100644
--- a/include/asm-generic/global_data.h
+++ b/include/asm-generic/global_data.h
@@ -150,7 +150,7 @@ typedef struct global_data {
#endif
/*
- * Global Data Flags - the top 16 bits are reserved for arch-specific flags
+ * Global Data Flags
*/
#define GD_FLG_RELOC 0x00001 /* Code was relocated to RAM */
#define GD_FLG_DEVINIT 0x00002 /* Devices have been initialized */
--
2.22.1
next prev parent reply other threads:[~2019-08-16 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 12:45 [U-Boot] [PATCH 1/2] x86: Remove x86 specific GD flags as they are not referenced at all Stefan Roese
2019-08-16 12:45 ` Stefan Roese [this message]
2019-08-16 14:51 ` [U-Boot] [PATCH 2/2] global_data: Remove comment of reserved arch-specific GD flags Bin Meng
2019-08-16 15:05 ` Simon Goldschmidt
2019-08-16 15:59 ` Simon Glass
2019-08-18 13:59 ` Bin Meng
2019-08-16 14:50 ` [U-Boot] [PATCH 1/2] x86: Remove x86 specific GD flags as they are not referenced at all Bin Meng
2019-08-16 15:03 ` Simon Goldschmidt
2019-08-18 13:59 ` Bin Meng
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=20190816124529.1178-2-sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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