From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Stepan Golosunov <stepan@golosunov.pp.ru>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] provide y2038 safe socket constants
Date: Tue, 31 Mar 2020 20:02:58 +0000 [thread overview]
Message-ID: <dc454c9b-d947-5fcc-6a27-1e6da8faecb5@synopsys.com> (raw)
In-Reply-To: <87r1x8qpx6.fsf@mid.deneb.enyo.de>
On 3/31/20 12:34 PM, Florian Weimer wrote:
> What about the parallel changes to the sysdeps overrides? I would> expect changes for hppa, mips, powerpc. (Not sure about the alpha
> situation.)
This patch fixes the existing/future asm-generic ABI enabled arches and the ones
you refer to are not. So IMHO that would be a separate patch if at all.
But if they do need fixing, I'm all up for it - except that I'm not sure if their
ABI is changing too. Which brings us (me) to a fundamental question, how are those
arches going to be made y2038 safe (me goes and reads the big wiki page)
Thx,
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2020-03-31 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 4:16 [PATCH] provide y2038 safe socket constants Vineet Gupta
2020-03-31 19:24 ` Vineet Gupta
2020-03-31 19:34 ` Florian Weimer
2020-03-31 20:02 ` Vineet Gupta [this message]
2020-03-31 20:18 ` Florian Weimer
2020-03-31 20:28 ` Vineet Gupta
2020-03-31 20:45 ` Joseph Myers
2020-03-31 21:00 ` Vineet Gupta
2020-03-31 21:22 ` Joseph Myers
2020-03-31 21:32 ` [PATCH v2] provide y2038 safe socket constants for default/asm-generic ABI Vineet Gupta
2020-04-06 18:55 ` Vineet Gupta
2020-04-13 21:11 ` Vineet Gupta
2020-04-17 23:20 ` Joseph Myers
2020-04-18 0:03 ` Vineet Gupta
2020-04-19 20:35 ` Vineet Gupta
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=dc454c9b-d947-5fcc-6a27-1e6da8faecb5@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=alistair.francis@wdc.com \
--cc=fw@deneb.enyo.de \
--cc=linux-snps-arc@lists.infradead.org \
--cc=stepan@golosunov.pp.ru \
/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