From: Andreas Schwab <schwab@suse.de>
To: Lukasz Majewski <lukma@denx.de>
Cc: Joseph Myers <joseph@codesourcery.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Alistair Francis <alistair23@gmail.com>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
Florian Weimer <fweimer@redhat.com>,
Florian Weimer <fw@deneb.enyo.de>,
Zack Weinberg <zackw@panix.com>,
Carlos O'Donell <carlos@redhat.com>,
Vineet Gupta <vineetg76@gmail.com>
Subject: Re: [PATCH 2/3] y2038: linux: Provide __lutimes64 implementation
Date: Mon, 02 Mar 2020 17:05:00 -0000 [thread overview]
Message-ID: <mvm5zfmd6wz.fsf@suse.de> (raw)
In-Reply-To: <20200217131735.18180-3-lukma@denx.de> (Lukasz Majewski's message of "Mon, 17 Feb 2020 14:17:34 +0100")
Ok.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2020-03-02 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:18 [PATCH 0/3] y2038: Conversion of [lf]utimes[at] to support 64 bit time Lukasz Majewski
2020-02-17 13:18 ` [PATCH 1/3] y2038: linux: Provide __futimes64 implementation Lukasz Majewski
2020-02-28 17:06 ` Lukasz Majewski
2020-03-02 17:05 ` Andreas Schwab
2020-07-06 22:58 ` Vineet Gupta
2020-07-07 7:21 ` Lukasz Majewski
2020-07-07 18:25 ` Vineet Gupta
2020-07-07 20:36 ` Joseph Myers
2020-07-08 6:58 ` Lukasz Majewski
2020-02-17 13:18 ` [PATCH 3/3] y2038: linux: Provide __futimesat64 implementation Lukasz Majewski
2020-02-28 17:07 ` Lukasz Majewski
2020-03-02 17:05 ` Andreas Schwab
2020-02-17 13:18 ` [PATCH 2/3] y2038: linux: Provide __lutimes64 implementation Lukasz Majewski
2020-02-28 17:06 ` Lukasz Majewski
2020-03-02 17:05 ` Andreas Schwab [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=mvm5zfmd6wz.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=lukma@denx.de \
--cc=siddhesh@gotplt.org \
--cc=vineetg76@gmail.com \
--cc=zackw@panix.com \
/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).