public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v7 01/16] Add SAFE_STATX macro
Date: Wed, 9 Oct 2024 11:12:15 +0200	[thread overview]
Message-ID: <ZwZI70OpzHyEtZqs@yuki.lan> (raw)
In-Reply-To: <20241009-listmount_statmount-v7-1-d5ad31d47f68@suse.com>

Hi!
> +LTP_DEFINE_STATX_STRUCT(statx_fallback);
> +
> +#ifdef HAVE_STRUCT_STATX
> +typedef struct statx ltp_statx_;
> +#else
> +LTP_DEFINE_STATX_STRUCT(statx);
> +
> +typedef struct statx_fallback ltp_statx_;
>  #endif

Do we need these typedefs at all? We end up with statx structure defined
in all cases anyways, so we can just use that in the union instead and
we can do just:

LTP_DEFINE_STATX_STRUCT(statx_fallback);

#ifndef HAVE_STRUCT_STATX
LTP_DEFINE_STATX_STRUCT(statx);
#endif

struct ltp_statx {
	union {
		struct statx buf;
		struct statx_fallback fallback;
	};
};

Which will create exactly the same result with less complexity (note
that if there is no system statx definition the statx and statx_fallback
structures are identical).

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2024-10-09  9:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  8:29 [LTP] [PATCH v7 00/16] statmount/listmount testing suites Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 01/16] Add SAFE_STATX macro Andrea Cervesato
2024-10-09  9:12   ` Cyril Hrubis [this message]
2024-10-09  8:29 ` [LTP] [PATCH v7 02/16] Add TST_EXP_EQ_STR macro Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 03/16] Add listmount/statmount syscalls Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 04/16] Add listmount/statmount fallback declarations Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 05/16] Add listmount01 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 06/16] Add listmount02 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 07/16] Add statmount01 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 08/16] Add statmount02 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 09/16] Add statmount03 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 10/16] Add statmount04 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 11/16] Add statmount05 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 12/16] Add statmount06 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 13/16] Add statmount07 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 14/16] Add statmount08 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 15/16] Add listmount03 test Andrea Cervesato
2024-10-09  8:29 ` [LTP] [PATCH v7 16/16] Add listmount04 test Andrea Cervesato
2024-10-09 10:45   ` 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=ZwZI70OpzHyEtZqs@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --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