public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH 2/2] tests: timestamp example
Date: Mon, 30 Jun 2025 10:20:45 -0600	[thread overview]
Message-ID: <accdc66c-1ee4-44af-9555-be2bd9236e25@kernel.dk> (raw)
In-Reply-To: <4ba2daee657f4ff41fe4bcae1f75bc0ad7079d6d.1751299730.git.asml.silence@gmail.com>

On 6/30/25 10:09 AM, Pavel Begunkov wrote:
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>

A bit of commit message might be nice? Ditto the other patch.
I know they are pretty straight forward, but doesn't hurt to
spell out a bit why the change is being made.

> +#ifndef SCM_TS_OPT_ID
> +#define SCM_TS_OPT_ID 0
> +#endif

This one had me a bit puzzled, particularly with:

> +	if (SCM_TS_OPT_ID == 0) {
> +		fprintf(stderr, "no SCM_TS_OPT_ID, skip\n");
> +		return T_EXIT_SKIP;
> +	}

as that'll just make the test skip on even my debian unstable/testing
base as it's still not defined there. But I guess it's because it's arch
specific? FWIW, looks like anything but sparc/parisc define it as 81,
hence in terms of coverage might be better to simply define it for
anything but those and actually have the test run?

-- 
Jens Axboe

  reply	other threads:[~2025-06-30 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 16:09 [PATCH 0/2] add tx timestamp tests Pavel Begunkov
2025-06-30 16:09 ` [PATCH 1/2] Sync io_uring.h with tx timestamp api Pavel Begunkov
2025-06-30 16:09 ` [PATCH 2/2] tests: timestamp example Pavel Begunkov
2025-06-30 16:20   ` Jens Axboe [this message]
2025-06-30 16:45     ` Pavel Begunkov
2025-06-30 16:47       ` Jens Axboe
2025-06-30 16:50       ` Pavel Begunkov
2025-06-30 16:54         ` Jens Axboe
2025-06-30 16:55         ` Pavel Begunkov

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=accdc66c-1ee4-44af-9555-be2bd9236e25@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=io-uring@vger.kernel.org \
    /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