All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Villemoes <ravi@prevas.dk>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de,  Tom Rini <trini@konsulko.com>
Subject: Re: [RFC PATCH 6/9] linker_lists.rst: update documentation
Date: Tue, 26 May 2026 23:49:54 +0200	[thread overview]
Message-ID: <87zf1let8d.fsf@prevas.dk> (raw)
In-Reply-To: <CAFLszTg2+hNfoBzMYiaSqad3G=JU40Qy+7oXXyUJxgH0Gk=Esg@mail.gmail.com> (Simon Glass's message of "Mon, 25 May 2026 09:03:11 -0600")

On Mon, May 25 2026, Simon Glass <sjg@chromium.org> wrote:

>>
>> -  __u_boot_list_ + 2_ + @_list + _2_ + @_entry
>> +  __u_boot_list_ + @_list + _2_ + @_entry
>>
>>  and the C variable name is
>>
>>  ::
>>
>> -  _u_boot_list + _2_ + @_list + _2_ + @_entry
>> +  _u_boot_list + @_list + _2_ + @_entry
>
> Not quite - the actual symbol is _u_boot_list_##_list##_2_##_name
> (note the trailing underscore on the prefix), so for list 'drivers'
> and entry 'first' the name expands to _u_boot_list_drivers_2_first
>
> As written here, the components concatenate to
> _u_boot_listdrivers_2_first - please change to:
>
>     _u_boot_list_ + @_list + _2_ + @_entry
>
> to match the section line above and the unified '%u_boot_list_ + ...'
> form a few lines later.

Good catch, I hadn't noticed the inconsistency in how the existing
section versus symbol names were documented.

>> diff --git a/doc/api/linker_lists.rst b/doc/api/linker_lists.rst
>> @@ -46,16 +46,8 @@ Start and end symbols for a list can generally be defined as
>>
>>  ::
>>
>> -  %u_boot_list_2_ + @_list + _1_...
>> -  %u_boot_list_2_ + @_list + _3_...
>> -
>> -Start and end symbols for the whole of the linker lists area can be
>> -defined as
>> -
>> -::
>> -
>> -  %u_boot_list_1_...
>> -  %u_boot_list_3_...
>> +  %u_boot_list_ + @_list + _1_...
>> +  %u_boot_list_ + @_list + _3_...
>
> The commit message says the surrounding 'Note the two _2_ constant
> components' paragraph is now easier to grok because only one such
> component remains, but the paragraph itself still says 'two' in the
> patched file. Please update it to say 'one' and adjust the rest of the
> sentence, since the start/end mapping is now relative to the single
> _2_ separator between list and entry.

Ah, yes, that does require rewording to make sense.

>> diff --git a/doc/api/linker_lists.rst b/doc/api/linker_lists.rst
>> @@ -82,19 +74,19 @@ defined for the whole list and each sub-list:
>> -  %u_boot_list_2_drivers_2_i2c_2_first
>> -  %u_boot_list_2_drivers_2_i2c_2_first
>> -  %u_boot_list_2_drivers_2_i2c_2_second
>> +  %u_boot_list_drivers_2_i2c_1
>> +  %u_boot_list_drivers_2_i2c_2_first
>> +  %u_boot_list_drivers_2_i2c_2_first
>> +  %u_boot_list_drivers_2_i2c_2_second
>
> BTW '...i2c_2_first' is listed twice - please drop the duplicate at
> the same time.
>

Will do.

Thanks,
Rasmus

  reply	other threads:[~2026-05-26 21:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 21:27 [RFC PATCH 0/9] linker list sanity checking Rasmus Villemoes
2026-05-22 21:27 ` [RFC PATCH 1/9] sandbox: Drop special link order treatment of start.o and sdl.o Rasmus Villemoes
2026-05-25 14:30   ` Simon Glass
2026-05-22 21:27 ` [RFC PATCH 2/9] linker_lists: Do not set "unused" attribute Rasmus Villemoes
2026-05-25 15:02   ` Simon Glass
2026-05-25 15:22     ` Tom Rini
2026-05-25 15:33       ` Simon Glass
2026-05-25 15:46         ` Tom Rini
2026-05-22 21:27 ` [RFC PATCH 3/9] event: Remove obsolete comment and __used attributes Rasmus Villemoes
2026-05-25 14:31   ` Simon Glass
2026-05-22 21:27 ` [RFC PATCH 4/9] linker_lists.h: add ll_*_name() helper macros Rasmus Villemoes
2026-05-22 22:44   ` Tom Rini
2026-05-25 14:32   ` Simon Glass
2026-05-22 21:27 ` [RFC PATCH 5/9] linker_lists.h: drop _2 from section and symbol name prefix Rasmus Villemoes
2026-05-22 22:44   ` Tom Rini
2026-05-25 15:02   ` Simon Glass
2026-05-26 21:44     ` Rasmus Villemoes
2026-05-27  4:41       ` Simon Glass
2026-05-22 21:27 ` [RFC PATCH 6/9] linker_lists.rst: update documentation Rasmus Villemoes
2026-05-22 22:45   ` Tom Rini
2026-05-25 15:03   ` Simon Glass
2026-05-26 21:49     ` Rasmus Villemoes [this message]
2026-05-22 21:27 ` [RFC PATCH 7/9] test: avoid use of special characters in ELF section names Rasmus Villemoes
2026-05-22 22:45   ` Tom Rini
2026-05-25 15:03   ` Simon Glass
2026-05-22 21:27 ` [RFC PATCH 8/9] linker_lists.h: emit lots of meta-data for debugging and sanity checking Rasmus Villemoes
2026-05-25 14:28   ` Simon Glass
2026-05-26 22:26     ` Rasmus Villemoes
2026-05-26 22:41       ` Rasmus Villemoes
2026-05-27  4:09         ` Simon Glass
2026-05-22 21:27 ` [RFC PATCH 9/9] tools: add linker-lists.py parser/checker script Rasmus Villemoes
2026-05-25 15:04   ` Simon Glass

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=87zf1let8d.fsf@prevas.dk \
    --to=ravi@prevas.dk \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --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 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.