aboutsummaryrefslogtreecommitdiffstats
path: root/lib/dump_stack.c
diff options
context:
space:
mode:
authorJohn Ogness <[email protected]>2024-02-07 13:40:54 +0000
committerPetr Mladek <[email protected]>2024-02-07 16:23:18 +0000
commit5113cf5f4c53eb2901ddb8fa70b72e8b6f4084ac (patch)
tree8cb878d17b1bdddc6b16f25d9125854b6a687526 /lib/dump_stack.c
parentprintk: ringbuffer: Do not skip non-finalized records with prb_next_seq() (diff)
downloadkernel-5113cf5f4c53eb2901ddb8fa70b72e8b6f4084ac.tar.gz
kernel-5113cf5f4c53eb2901ddb8fa70b72e8b6f4084ac.zip
printk: ringbuffer: Clarify special lpos values
For empty line records, no data blocks are created. Instead, these valid records are identified by special logical position values (in fields of @prb_desc.text_blk_lpos). Currently the macro NO_LPOS is used for empty line records. This name is confusing because it does not imply _why_ there is no data block. Rename NO_LPOS to EMPTY_LINE_LPOS so that it is clear why there is no data block. Also add comments explaining the use of EMPTY_LINE_LPOS as well as clarification to the values used to represent data-less blocks. Signed-off-by: John Ogness <[email protected]> Reviewed-by: Petr Mladek <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'lib/dump_stack.c')
0 files changed, 0 insertions, 0 deletions