Skip to contentSkip to conversation

docs/devel: be consistent about example plugin names

PATCH Applied Mahmoud Mandour 2 participants 2 messages Aug 30, 2021 – Sep 1, 2021

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs/devel: be consistent about example plugin names

Some plugins were prefixed with .c, some were not. Since the name is essentially the full-name of the plugin file, it's logical to include the extension.

---
 docs/devel/tcg-plugins.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/devel/tcg-plugins.rst +2 -2
index 047bf4ada7..f96aad4ae7 100644
@@ -286,7 +286,7 @@ which will eventually report::
     previously @ 0x000000ffd08098/5 (809900593 insns)
     previously @ 0x000000ffd080c0/1 (809900588 insns)
 
-- contrib/plugins/hwprofile
+- contrib/plugins/hwprofile.c
 
 The hwprofile tool can only be used with system emulation and allows
 the user to see what hardware is accessed how often. It has a number of options:
@@ -345,7 +345,7 @@ which will output an execution trace following this structure::
   0, 0xd34, 0xf9c8f000, "bl #0x10c8"
   0, 0x10c8, 0xfff96c43, "ldr r3, [r0, #0x44]", load, 0x200000e4, RAM
 
-- contrib/plugins/cache
+- contrib/plugins/cache.c
 
 Cache modelling plugin that measures the performance of a given cache
 configuration when a given working set is run::
Signature · 1 line
2.33.0
Applied
#1 lore raw
Quoted 5 lines · Mahmoud Mandour

Some plugins were prefixed with .c, some were not. Since the name is essentially the full-name of the plugin file, it's logical to include the extension.

Queued to pr/010921-for-6.2-1, thanks.

Signature · 1 line
Alex Bennée