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 X-Spam-Level: X-Spam-Status: No, score=-9.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6D69AC0650E for ; Mon, 8 Jul 2019 01:49:51 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E6DCB20673 for ; Mon, 8 Jul 2019 01:49:50 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E6DCB20673 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 45hpKn0RXRzDqJL for ; Mon, 8 Jul 2019 11:49:49 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 45hng14tCDzDqQM for ; Mon, 8 Jul 2019 11:19:41 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: by ozlabs.org (Postfix, from userid 1034) id 45hng007V0z9sNy; Mon, 8 Jul 2019 11:19:39 +1000 (AEST) X-powerpc-patch-notification: thanks X-powerpc-patch-commit: 259a948c4ba1829ae4a3c31bb6e40ad458a21254 In-Reply-To: <20190607064705.29043-1-aneesh.kumar@linux.ibm.com> To: "Aneesh Kumar K.V" , npiggin@gmail.com, paulus@samba.org, oohall@gmail.com From: Michael Ellerman Subject: Re: [PATCH] powerpc/scm: Use a specific endian format for storing uuid from the device tree Message-Id: <45hng007V0z9sNy@ozlabs.org> Date: Mon, 8 Jul 2019 11:19:39 +1000 (AEST) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Aneesh Kumar K.V" , linuxppc-dev@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Fri, 2019-06-07 at 06:47:05 UTC, "Aneesh Kumar K.V" wrote: > We used uuid_parse to convert uuid string from device tree to two u64 > components. We want to make sure we look at the uuid read from device > tree in an endian-neutral fashion. For now, I am picking little-endian > to be format so that we don't end up doing an additional conversion. > > The reason to store in a specific endian format is to enable reading > the namespace created with a little-endian kernel config on a big-endian kernel. > We do store the device tree uuid string as a 64-bit little-endian cookie in the > label area. When booting the kernel we also compare this cookie > against what is read from the device tree. For this, to work we have > to store and compare these values in a CPU endian config independent fashion. > > Signed-off-by: Aneesh Kumar K.V Applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/259a948c4ba1829ae4a3c31bb6e40ad458a21254 cheers