From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 35BE4C83F18 for ; Tue, 29 Aug 2023 13:19:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235931AbjH2NTG (ORCPT ); Tue, 29 Aug 2023 09:19:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45508 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235941AbjH2NSu (ORCPT ); Tue, 29 Aug 2023 09:18:50 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F321F7; Tue, 29 Aug 2023 06:18:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1693315128; x=1724851128; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=7J2QJDwfsMXgCfWqfJMKUpM0mvVbSNEniUpWtVl4Uzw=; b=azbDd4i1GJgBZYSFbc/Uxi832wh/m3V4j8Tkua2gQXc5+oncWB2aF7fc tpz6c2paVNxMlDh8Hhlq1t5kZqj971pbYLA6eHL1P2IMuKwG5wwqI8r2Y OOZ0LrhB2GQp+Tc45ZzJD6fKEPtqmUTNr9AuOmpLnm8bTffttyRX50By0 dOfaHbqdtu8fA6LXoTsal4m+EzW5B62UIQj0TvZDsJx5NYLpcM/96ANR1 m5tJCf1/64MG03SKq5IWRm0iiFetYP5R+nIwQE8hrPrq6Vnb1Jg0VJQix DIRiuxJt/7mY+kupvTmRD5crONnnQ5D6fokNyMEuymvG+T2DX1n8QRcnK A==; X-IronPort-AV: E=McAfee;i="6600,9927,10817"; a="372776934" X-IronPort-AV: E=Sophos;i="6.02,210,1688454000"; d="scan'208";a="372776934" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Aug 2023 06:18:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10817"; a="808662221" X-IronPort-AV: E=Sophos;i="6.02,210,1688454000"; d="scan'208";a="808662221" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga004.fm.intel.com with ESMTP; 29 Aug 2023 06:18:44 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qaycE-004t5p-2s; Tue, 29 Aug 2023 16:18:42 +0300 Date: Tue, 29 Aug 2023 16:18:42 +0300 From: Andy Shevchenko To: Jonathan Cameron Cc: Jonathan Cameron , Lorenzo Bianconi , Philipp Jungkamp , Peter Zijlstra , linux-input@vger.kernel.org, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, Jiri Kosina , Srinivas Pandruvada , Lars-Peter Clausen Subject: Re: [PATCH v1 2/3] iio: imu: st_lsm6dsx: Use aligned data type for timestamp Message-ID: References: <20230815154027.12468-1-andriy.shevchenko@linux.intel.com> <20230815154027.12468-2-andriy.shevchenko@linux.intel.com> <20230828170341.3a9641f0@jic23-huawei> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230828170341.3a9641f0@jic23-huawei> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On Mon, Aug 28, 2023 at 05:03:41PM +0100, Jonathan Cameron wrote: > On Tue, 15 Aug 2023 18:40:26 +0300 > Andy Shevchenko wrote: ... > > struct { > > __le16 channels[3]; > > - s64 ts __aligned(8); > > + __aligned_s64 ts; > > aligned_s64 as it's internal to the kernel? Either works, but strictly speaking you are right, better no underscored variant. > > } scan[ST_LSM6DSX_ID_MAX]; -- With Best Regards, Andy Shevchenko