public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4] linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ #28350)
Date: Thu, 27 Jan 2022 14:32:06 +0100	[thread overview]
Message-ID: <87tudpmhih.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <16fe263b-fc7a-81ba-dd0e-0979f071a409@linaro.org> (Adhemerval Zanella's message of "Thu, 27 Jan 2022 09:19:27 -0300")

* Adhemerval Zanella:

>> Right, I expected something like that, which is why I insisted on adding
>> the time64 symbol aliases.
>
> I can work on a patch for 2.35 if you think this is really required.  Another
> options would just to remove the MSG_CTRUNC fro 2.35.

I really want that fix, but I think we can backport it just after the
release.

Thanks,
Florian


  reply	other threads:[~2022-01-27 13:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 18:52 Adhemerval Zanella
2022-01-12 13:36 ` Adhemerval Zanella
2022-01-21 13:53 ` Florian Weimer
2022-01-24 12:07   ` Adhemerval Zanella
2022-01-24 12:13     ` Florian Weimer
2022-01-24 12:23       ` Adhemerval Zanella
2022-01-24 12:38         ` Florian Weimer
2022-01-24 13:26           ` Adhemerval Zanella
2022-01-26 20:48             ` Florian Weimer
2022-01-27 11:23               ` Adhemerval Zanella
2022-01-27 11:58                 ` Florian Weimer
2022-01-27 12:19                   ` Adhemerval Zanella
2022-01-27 13:32                     ` Florian Weimer [this message]
2022-01-27 13:55                       ` Adhemerval Zanella
2022-01-27 14:09                         ` Florian Weimer
2022-01-27 14:13                           ` Adhemerval Zanella
2022-01-27 14:17                             ` Adhemerval Zanella

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=87tudpmhih.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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).