mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jules Maselbas <jmaselbas@kalray.eu>
To: barebox@lists.infradead.org
Cc: Jules Maselbas <jmaselbas@kalray.eu>
Subject: [PATCH] Documentation: Replace ENTRY_POINT with ENTRY_FUNCTION
Date: Tue,  7 Sep 2021 15:01:30 +0200	[thread overview]
Message-ID: <20210907130131.26755-1-jmaselbas@kalray.eu> (raw)

I think the documentation is referring to the ENTRY_FUNCTION macro, not ENTRY_POINT

Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
---
 Documentation/devel/porting.rst    | 2 +-
 Documentation/user/multi-image.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devel/porting.rst b/Documentation/devel/porting.rst
index 97b787327c..5bf0b45e65 100644
--- a/Documentation/devel/porting.rst
+++ b/Documentation/devel/porting.rst
@@ -131,7 +131,7 @@ Lets look at this line by line:
  - ``ENTRY_FUNCTION(start_my_board, r0, r1, r2)``
    The entry point is special: It needs to be located at the beginning of the
    image, it does not return and may run before a stack is set up.
-   The ``ENTRY_POINT()`` macro takes care of these details and passes along
+   The ``ENTRY_FUNCTION()`` macro takes care of these details and passes along
    a number of registers, in case the Boot ROM has placed something interesting there.
 
  - ``extern char __dtb_my_board_start[];``
diff --git a/Documentation/user/multi-image.rst b/Documentation/user/multi-image.rst
index 727b98fe5a..0a7bf91a55 100644
--- a/Documentation/user/multi-image.rst
+++ b/Documentation/user/multi-image.rst
@@ -46,7 +46,7 @@ let the common binary determine the board type.
 
 The board specific PBL images are generated from a single set of object files
 using the linker. The basic trick here is that the PBL objects have multiple
-entry points, specified with the ENTRY_POINT macro. For each PBL binary
+entry points, specified with the ENTRY_FUNCTION macro. For each PBL binary
 generated a different entry point is selected using the ``-e`` option to ld.
 The linker will throw away all unused entry points and only keep the functions
 used by a particular entry point.
-- 
2.17.1


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


             reply	other threads:[~2021-09-07 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 13:01 Jules Maselbas [this message]
2021-09-07 13:01 ` [PATCH] Documentation: Typo fix in command example Jules Maselbas
2021-09-08  8:41   ` Jules Maselbas
2021-10-04 10:10     ` 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=20210907130131.26755-1-jmaselbas@kalray.eu \
    --to=jmaselbas@kalray.eu \
    --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