Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lib: Add tst_sysfs_assert
Date: Thu, 20 Aug 2026 07:58:08 +0000	[thread overview]
Message-ID: <20260820075808.9294-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260819161634.1341577-4-chrubis@suse.cz>

Hi Cyril,

On Wed, 19 Aug 2026 18:16:04 +0200, Cyril Hrubis wrote:
> lib: Add tst_sysfs_assert

--- [PATCH 1/31] ---

> +/**
> + * tst_sysfs_exists() - Checks whether a file exists.
> + *
> + *
> + * @fmt: A printf-like format to build a path to the file.
> + * @...: A printf-like parameters for fmt.
> + * return: 1 if the file at the path built from fmt exists, 0 otherwise.
> + */

Since kernel-doc section labels are case-sensitive, should this be "Return:"
(capital R) instead of "return:"?

Could the stray blank " *" line between the summary and the @parameters
also be removed?

--- [PATCH 14/31] ---

> testcases: sysfs: sys_hwmon01

Could the subject describe the change by adding "Add", consistently with
the other test-adding commits in the series, i.e.
"testcases: sysfs: Add sys_hwmon01"?

--- [PATCH 15/31] ---

> testcases: sysfs: sys_leds01

Could "Add" be included here as well, i.e.
"testcases: sysfs: Add sys_leds01"?

--- [PATCH 19/31] ---

> +/*
> + * Change the link-layer (MAC) address of an existing network device.
> ...
> +int tst_netdev_set_hwaddr(const char *file, const int lineno, int strict,
> +	const char *ifname, const void *addr, size_t addrlen);

> +/*
> + * Enslave ifname to the master_ifname device, e.g. add it as a bridge
> ...
> +int tst_netdev_set_master(const char *file, const int lineno, int strict,
> +	const char *ifname, const char *master_ifname);

Could both new public functions use kernel-doc /** comments instead of
plain /* comments so they appear in the generated API documentation?

--- [PATCH 22/31] ---

> Similar to sys_net02 but checks bridge related files after briding a
> virtual ethernet interface.

Could "briding" be changed to "bridging"?

--- [PATCH 23/31] ---

> +static void cleanup(void)
> +{
> +	if (tun_fd >= 0)
> +		SAFE_CLOSE(tun_fd);
> +
> +	if (tap_fd >= 0)
> +		SAFE_CLOSE(tap_fd);

Since both variables are initialized to -1, could these guards use the LTP
"fd != -1" convention instead of "fd >= 0"?

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-08-20  7:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 16:16 [LTP] [PATCH v1 00/31] Add sysfs sanity tests Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 01/31] lib: Add tst_sysfs_assert Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 02/31] testcases: sysfs: Add sys_power01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 03/31] testcases: sysfs: Add sys_kernel01 Cyril Hrubis
2026-08-20  7:58   ` linuxtestproject.agent [this message]
2026-08-19 16:16 ` [LTP] [PATCH v2 04/31] testcases: sysfs: Add sys_clocksource01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 05/31] testcases: sysfs: Add sys_node01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 06/31] testcases: sysfs: Add sys_cpu_topology01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 07/31] testcases: sysfs: Add sys_cpu_topology02 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 08/31] testcases: sysfs: Add sys_cpu_vulnerabilities01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 09/31] testcases: sysfs: Add sys_cpu_smt01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 10/31] testcases: sysfs: Add sys_cpu_cache01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 11/31] testcases: sysfs: Add sys_clockevents01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 12/31] testcases: sysfs: Add sys_ata01 Cyril Hrubis
2026-08-20 15:57   ` Petr Vorel
2026-08-20 16:21     ` Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 13/31] testcases: sysfs: Add sys_bdi01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 14/31] testcases: sysfs: sys_hwmon01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 15/31] testcases: sysfs: sys_leds01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 16/31] testcases: sysfs: Add sys_wakeup01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 17/31] testcases: sysfs: Add sys_rtc01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 18/31] testcases: sysfs: Add sys_thermal01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 19/31] tst_netdevice: Add two more helper macros Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 20/31] testcases: sysfs: Add sys_net01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 21/31] testcases: sysfs: Add sys_net02 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 22/31] testcases: sysfs: Add sys_net03 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 23/31] testcases: sysfs: Add sys_net04 Cyril Hrubis
2026-08-19 20:20   ` Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 24/31] testcases: sysfs: Add sys_block_loop01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 25/31] testcases: sysfs: Add sys_block_queue01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 26/31] testcases: sysfs: Add sys_block_size01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 27/31] testcases: sysfs: Add sys_hugepages01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 28/31] testcases: sysfs: Add sys_hugepages02 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 29/31] testcases: sysfs: Add sys_ksm01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 30/31] testcases: sysfs: Add sys_swap01 Cyril Hrubis
2026-08-19 16:16 ` [LTP] [PATCH v2 31/31] testcases: sysfs: Add sys_thp01 Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2026-08-18 14:12 [LTP] [PATCH v1 03/31] testcases: sysfs: Add sys_kernel01 Cyril Hrubis
2026-08-18 14:54 ` [LTP] lib: Add tst_sysfs_assert linuxtestproject.agent
2026-08-19 16:13   ` Cyril Hrubis

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=20260820075808.9294-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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