public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Dan Christensen <opello@opello.org>
Cc: libc-help@sourceware.org
Subject: Re: clock_gettime after 2.31 and reused syscall numbers
Date: Thu, 22 Dec 2022 20:04:01 +0100	[thread overview]
Message-ID: <877cyjmfa6.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAKUTJ2sciOs-SDjfv_G-wesqr9c5tfEN88COUFSAcDG6LdgX3w@mail.gmail.com> (Dan Christensen's message of "Thu, 22 Dec 2022 12:18:05 -0600")

* Dan Christensen:

> Or is all of that out of scope because "a vendor deviated from
> mainline, and such things are impossible to predict or support"?

Yes, that's basically it.  If the system calls do not work as in
mainline Linux, there is little we can do about it.

In this particular case, it only affects 32-bit and no major
distribution kernels, so there isn't a very compelling reason to support
this.

Thanks,
Florian


      reply	other threads:[~2022-12-22 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 18:18 Dan Christensen
2022-12-22 19:04 ` Florian Weimer [this message]

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=877cyjmfa6.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=opello@opello.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).