From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: Jordan Justen <jljusten@debian.org>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [PATCH i-g-t] tools: rename lsfacts into igt_facts
Date: Tue, 18 Feb 2025 08:32:08 +0100 [thread overview]
Message-ID: <32a9510b-a18b-40c7-8f70-8d59b501df48@linux.intel.com> (raw)
In-Reply-To: <20250217133229.104948-1-kamil.konieczny@linux.intel.com>
On 17.02.2025 14:32, Kamil Konieczny wrote:
> This is a follow up to GitLab issue 168 where name 'power' was
> a little too generic. Similarly, name lsfacts looks also a little
> too generic, so rename it into igt_facts.
Would you consider keeping the 'ls' part of the name so that it would
be called 'igt_lsfacts'? The reason is that the tool simply list facts,
while the integration with igt_runner report changes instead of listing
facts.
May I ask why the lsgpu tool did not get a rename too? Would a rename to
'igt_lsgpu' help prevent name collisions with system wide tools that have
similar objectives?
>
> Cc: Jordan Justen <jljusten@debian.org>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>
Acked-by: Peter Senna Tschudin <peter.senna@linux.intel.com>
Reviewed-by: Peter Senna Tschudin <peter.senna@linux.intel.com>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
> tools/{lsfacts.c => igt_facts.c} | 12 ++++++------
> tools/meson.build | 2 +-
> 2 files changed, 7 insertions(+), 7 deletions(-)
> rename tools/{lsfacts.c => igt_facts.c} (71%)
>
> diff --git a/tools/lsfacts.c b/tools/igt_facts.c
> similarity index 71%
> rename from tools/lsfacts.c
> rename to tools/igt_facts.c
> index bbe77717a..af3ea2a61 100644
> --- a/tools/lsfacts.c
> +++ b/tools/igt_facts.c
> @@ -7,12 +7,12 @@
> #include "igt_facts.h"
>
> /**
> - * SECTION:lsfacts
> - * @short_description: lsfacts
> - * @title: lsfacts
> - * @include: lsfacts.c
> + * SECTION:igt_facts
> + * @short_description: igt_facts
> + * @title: igt_facts
> + * @include: igt_facts.c
> *
> - * # lsfacts
> + * # igtfacts
> *
> * Scan for igt-facts and print them on screen. Indicate if no facts are found.
> */
> @@ -20,7 +20,7 @@ int main(int argc, char *argv[])
> {
> igt_facts_lists_init();
>
> - igt_facts("lsfacts");
> + igt_facts("igt_facts");
>
> if (igt_facts_are_all_lists_empty())
> igt_info("No facts found...\n");
> diff --git a/tools/meson.build b/tools/meson.build
> index f091af380..1dfe1f839 100644
> --- a/tools/meson.build
> +++ b/tools/meson.build
> @@ -12,6 +12,7 @@ foreach prog : tools_progs_noisnt
> endforeach
>
> tools_progs = [
> + 'igt_facts',
> 'igt_power',
> 'igt_stats',
> 'intel_audio_dump',
> @@ -43,7 +44,6 @@ tools_progs = [
> 'intel_gem_info',
> 'intel_gvtg_test',
> 'dpcd_reg',
> - 'lsfacts',
> 'lsgpu',
> ]
> tool_deps = igt_deps
next prev parent reply other threads:[~2025-02-18 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:32 [PATCH i-g-t] tools: rename lsfacts into igt_facts Kamil Konieczny
2025-02-17 14:36 ` ✗ GitLab.Pipeline: warning for " Patchwork
2025-02-17 14:51 ` ✗ i915.CI.BAT: failure " Patchwork
2025-02-18 16:11 ` Kamil Konieczny
2025-02-17 15:04 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-18 3:25 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-18 16:12 ` Kamil Konieczny
2025-02-18 7:32 ` Peter Senna Tschudin [this message]
2025-02-18 7:37 ` [PATCH i-g-t] " Peter Senna Tschudin
2025-02-18 16:09 ` Kamil Konieczny
2025-02-18 16:06 ` Kamil Konieczny
2025-02-19 22:39 ` Jordan Justen
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=32a9510b-a18b-40c7-8f70-8d59b501df48@linux.intel.com \
--to=peter.senna@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jljusten@debian.org \
--cc=jordan.l.justen@intel.com \
--cc=kamil.konieczny@linux.intel.com \
/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