Searched hist:a48849e2358ecf1a347a03b33dc27b9b2f25f8fd (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/Documentation/core-api/ |
H A D | printk-formats.rst | diff a48849e2358ecf1a347a03b33dc27b9b2f25f8fd Thu Feb 25 10:46:39 CST 2021 Vlastimil Babka <vbabka@suse.cz> printk: clarify the documentation for plain pointer printing
We have several modifiers for plain pointers (%p, %px and %pK) and now also the no_hash_pointers boot parameter. The documentation should help to choose which variant to use. Importantly, we should discourage %px in favor of %p (with the new boot parameter when debugging), and stress that %pK should be only used for procfs and similar files, not dmesg buffer. This patch clarifies the documentation in that regard.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org> Reviewed-by: Petr Mladek <pmladek@suse.com> Signed-off-by: Petr Mladek <pmladek@suse.com> Link: https://lore.kernel.org/r/20210225164639.27212-1-vbabka@suse.cz
|
/openbmc/linux/lib/ |
H A D | vsprintf.c | diff a48849e2358ecf1a347a03b33dc27b9b2f25f8fd Thu Feb 25 10:46:39 CST 2021 Vlastimil Babka <vbabka@suse.cz> printk: clarify the documentation for plain pointer printing
We have several modifiers for plain pointers (%p, %px and %pK) and now also the no_hash_pointers boot parameter. The documentation should help to choose which variant to use. Importantly, we should discourage %px in favor of %p (with the new boot parameter when debugging), and stress that %pK should be only used for procfs and similar files, not dmesg buffer. This patch clarifies the documentation in that regard.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org> Reviewed-by: Petr Mladek <pmladek@suse.com> Signed-off-by: Petr Mladek <pmladek@suse.com> Link: https://lore.kernel.org/r/20210225164639.27212-1-vbabka@suse.cz
|