LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnd Bergmann <email@example.com>
To: James Hogan <firstname.lastname@example.org>
Cc: Ralf Baechle <email@example.com>,
"open list:RALINK MIPS ARCHITECTURE" <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>,
Paul Burton <firstname.lastname@example.org>,
Matt Redfearn <email@example.com>,
Marcin Nowakowski <firstname.lastname@example.org>,
Matthew Fortune <Matthew.Fortune@mips.com>
Subject: Re: Introducing a nanoMIPS port for Linux
Date: Fri, 4 May 2018 19:53:04 -0400 [thread overview]
Message-ID: <CAK8P3a1BvG+jHAmQu2j-_Gmmxc4s_KbccUGP0jvPGq6Lemail@example.com> (raw)
On Fri, May 4, 2018 at 9:24 AM, James Hogan <firstname.lastname@example.org> wrote:
> On Thu, May 03, 2018 at 06:40:07PM -0400, Arnd Bergmann wrote:
>> On Wed, May 2, 2018 at 5:51 PM, James Hogan <email@example.com> wrote:
>> While I haven't looked at the individual changes, I wonder whether
>> it would be useful to make this new ABI use 64-bit time_t from
>> the start, using the new system calls that Deepa and I have been
>> posting recently.
> Personally I'm all for squeezing as much API cleanup in as possible
> before its merged, though obviously there'll be a point when the ABI may
> need to be frozen, at which point we'll mostly have to accept what we
> have within reason.
>> There are still a few things to be worked out:
>> only the first of four sets of syscall patches is merged so far,
>> and we have a couple of areas that will require further ABI changes
>> (sound, sockets, media and maybe a couple of smaller drivers),
>> so it depends on the overall timing. If you would otherwise merge
>> the patches quickly, then it may be better to just follow the existing
>> 32-bit architectures and add the 64-bit entry points when we do it
>> for everyone.
> I think it'll likely be a couple of cycles before it gets merged anyway.
> There's still work to do, and limited resources.
Ok, let's plan on getting the 64-bit time_t ABIs in place early enough
then. We will likely have very similar timing for the upcoming rv32
ABI on arch/riscv.
prev parent reply other threads:[~2018-05-04 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 21:51 James Hogan
2018-05-03 22:40 ` Arnd Bergmann
2018-05-04 13:24 ` James Hogan
2018-05-04 23:53 ` Arnd Bergmann [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: Introducing a nanoMIPS port for Linux' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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 NNTP newsgroup(s).