From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751939AbcGRTGB (ORCPT ); Mon, 18 Jul 2016 15:06:01 -0400 Received: from mga03.intel.com ([134.134.136.65]:3684 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751705AbcGRTF5 (ORCPT ); Mon, 18 Jul 2016 15:05:57 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,385,1464678000"; d="scan'208";a="1024255760" Date: Mon, 18 Jul 2016 22:05:19 +0300 From: Jarkko Sakkinen To: Jason Gunthorpe Cc: Andrey Pronin , Peter Huewe , Marcel Selhorst , tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, groeck@chromium.org, smbarber@chromium.org, dianders@chromium.org Subject: Re: [PATCH 2/2] tpm: fix byte-order for the value read by tpm2_get_tpm_pt Message-ID: <20160718190519.GM31463@intel.com> References: <1468544838-9990-1-git-send-email-apronin@chromium.org> <1468544838-9990-3-git-send-email-apronin@chromium.org> <20160715031046.GC9347@obsidianresearch.com> <20160715031701.GA25406@apronin> <20160715033553.GJ9347@obsidianresearch.com> <20160715193143.GA7052@apronin> <20160715193928.GA20719@obsidianresearch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160715193928.GA20719@obsidianresearch.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 15, 2016 at 01:39:28PM -0600, Jason Gunthorpe wrote: > On Fri, Jul 15, 2016 at 12:31:43PM -0700, Andrey Pronin wrote: > > > I even tried changing the code there to > > __be32 vv = cmd.params.get_tpm_pt_out.value; > > u32 ret = vv; > > to make it clear what's going on. Still, no complaints from sparse. > > Hum, I'm not an expert at sparse, but I expect a warning from it here? > > Maybe Jarkko knows when he gets back? I do run sparse regularly. If look at the commit log there are even couple of recent bug fixes related to sparse errors. /Jarkko