All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]].
Date: Thu, 19 Jun 2025 10:54:32 -0700	[thread overview]
Message-ID: <877c17liqv.fsf@gmail.com> (raw)
In-Reply-To: <tc6b4trkpv5sow3pxgul7i3rc6bjnz7iupryyqzx7a7hxkdnou@65zruztgsi5c>

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

Hi Alex,

Alejandro Colomar <alx@kernel.org> writes:

>> -.BI "int gettimeofday(struct timeval *restrict " tv ,
>> -.BI "                 struct timezone *_Nullable restrict " tz );
>> +.BI "[[deprecated]] int gettimeofday(struct timeval *restrict " tv ,
>
> Please put the attribute in a separate line, to avoid bad alignment.

I thought my patch had lines that were too long, but I wasn't sure of a
better way to format it. If I understand correctly, you suggest:

    .BI "[[deprecated]]"
    .BI "int gettimeofday(struct timeval *restrict " tv ,
    .BI "                 struct timezone *_Nullable restrict " tz );

But I think the [[deprecated]] looks a bit strange alone on that line.
Maybe the return type 'int' should be placed on the line with it. What
do you think?

>>  .BI "int settimeofday(const struct timeval *" tv ,
>>  .BI "                 const struct timezone *_Nullable " tz );
>
> Should settimeofday(2) be considered deprecated too, even if it was
> never standard?  It doesn't seem to make much sense to keep it intact if
> the get*() one is deprecated.

Sure, it seems pretty uncontroversial to deprecate it ourselves. In V2 I
can also add the [[deprecated]] there and recommend 'clock_settime'
instead in HISTORY.

I will wait for your input on the declaration formatting first though.

Collin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2025-06-19 17:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  4:22 [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]] Collin Funk
2025-06-19  4:22 ` [PATCH 2/3] man/man3/ftime.3: Declare ftime " Collin Funk
2025-06-23  0:45   ` Alejandro Colomar
2025-06-19  4:22 ` [PATCH 3/3] man/man3/ftime.3: Correct POSIX standards in HISTORY Collin Funk
2025-06-23  0:53   ` Alejandro Colomar
2025-06-23  2:48     ` Collin Funk
2025-06-19 11:12 ` [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]] Alejandro Colomar
2025-06-19 17:54   ` Collin Funk [this message]
2025-06-19 22:20     ` Alejandro Colomar
2025-06-19 22:55       ` Collin Funk
2025-06-19 22:43 ` [PATCH v2] man/man2/gettimeofday.2: Declare functions " Collin Funk
2025-06-23  0:42   ` Alejandro Colomar
2025-06-23  2:42     ` Collin Funk
2025-06-23  3:09       ` G. Branden Robinson

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=877c17liqv.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.