From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752292AbdKUCbI (ORCPT ); Mon, 20 Nov 2017 21:31:08 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:27098 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751876AbdKUCbG (ORCPT ); Mon, 20 Nov 2017 21:31:06 -0500 To: Satish Kharat Cc: Arnd Bergmann , Sesidhar Baddela , Karan Tilak Kumar , "James E.J. Bottomley" , "Martin K. Petersen" , Johannes Thumshirn , Deepa Dinamani , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] fnic: use 64-bit timestamps From: "Martin K. Petersen" Organization: Oracle Corporation References: <20171107104305.2952640-1-arnd@arndb.de> Date: Mon, 20 Nov 2017 21:30:49 -0500 In-Reply-To: <20171107104305.2952640-1-arnd@arndb.de> (Arnd Bergmann's message of "Tue, 7 Nov 2017 11:41:39 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Source-IP: userv0022.oracle.com [156.151.31.74] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > struct timespec is deprecated since it overflows in 2038 on 32-bit > architectures, so we should use timespec64 consistently. > > I'm slightly adapting the format strings here, to make sure we print > the nanoseconds with the correct number of leading zeroes. Satish: Please review/test. Thank you! -- Martin K. Petersen Oracle Linux Engineering