From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751848AbcFWHh6 (ORCPT ); Thu, 23 Jun 2016 03:37:58 -0400 Received: from mail-lf0-f52.google.com ([209.85.215.52]:33540 "EHLO mail-lf0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751782AbcFWHh4 (ORCPT ); Thu, 23 Jun 2016 03:37:56 -0400 MIME-Version: 1.0 In-Reply-To: <20160623073607.GA21325@yury-N73SV> References: <1466485631-3532-1-git-send-email-ynorov@caviumnetworks.com> <1466485631-3532-2-git-send-email-ynorov@caviumnetworks.com> <5769139E.7020805@arm.com> <20160623043542.GA13449@yury-N73SV> <20160623073607.GA21325@yury-N73SV> From: Andrew Pinski Date: Thu, 23 Jun 2016 00:37:54 -0700 Message-ID: Subject: Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons. To: Yury Norov Cc: Andreas Schwab , Szabolcs Nagy , GNU C Library , LKML , nd , Arnd Bergmann , Catalin Marinas , Marcus Shawcroft , philb@gnu.org, David Miller , Maxim Kuvyrkov , "Joseph S. Myers" , Andrew Pinski Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 23, 2016 at 12:36 AM, Yury Norov wrote: > On Thu, Jun 23, 2016 at 09:32:46AM +0200, Andreas Schwab wrote: >> Andrew Pinski writes: >> >> > So if you want aarch64 to be compatible with aarch32, you need to >> > define __WORDSIZE_TIME64_COMPAT32. If we don't want aarch64 and >> > aarch32 to be compatible at all, then we can drop this patch or if you >> > don't want LP64 and ILP32 to be compatible either. >> >> Or go the other way like s390 and use the LP64 layout for ILP32. >> >> 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." > > It was an agreement that we don't fix Y2038 issues specifically, as > there will be general fix. Except that was the agreement for ILP32 what about AARCH32 and AARCH64 LP64 where is a known issue right now. ARM and AARCH64 maintainers please chime in about this issue. Thanks, Andrew