Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp3102859pxb; Mon, 24 Jan 2022 02:29:01 -0800 (PST) X-Google-Smtp-Source: ABdhPJx21qA6YzecjKpjjazqpxsSDHh6NiQag6LHBZPTINqw5T1J0E/W6cxrB3nWLcLeQj4aAMP+ X-Received: by 2002:a17:902:ea05:b0:14b:4c26:f44a with SMTP id s5-20020a170902ea0500b0014b4c26f44amr4293813plg.100.1643020141101; Mon, 24 Jan 2022 02:29:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643020141; cv=none; d=google.com; s=arc-20160816; b=TF9LrUwVqqp5otMdUhkH6SjXqscEcrzfyilb0DW4qEmNFUg8YLLjhpuHorP058QtwH UBx8UPbL22t6i+IgVsSXaGYYnqcyI6L/7bcwpQA11lXQZ2ey245SisYTjrdk52XM1m3E bkrZpBHoQK2lh1ddktgbipu0sOLm0vDM7qei902Q2uWETZCizm0KKTSpGwmgssB7ojz4 HzC6jPg66nkR5wMJZXCst7aAvD4iMX48Qnh8T6N6ZY+zgQh2PoUk77EMrdY07njFQ/4b AxHYk0QYUE7HoXFPLYRIK+t5vibviX9EM9KdVFC/poEnqmSHwtAwZ8uF9ydjF8eK7wob +fdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:sender:dkim-signature; bh=IHqd7yX1XGLLOu24CAliRnIh4Fy6X/3R/a7MUMsmKr8=; b=kQSj8P/XhhAk1YQ+KiaezkK9NFKZom13IDgyOtza54ypHsm+v5rGdISHd8nSWjyRcR C0BcqrVMUiV75IWxxA5aexs1/Cj6Slv/TS7papIIu8fRfuQnQ6jGK7EoInSBPOwWZNt5 1cpt7ml2IHbawYmlr9BCgewuswMZlSAXMqm1T5XpzidRd8Ode1dTIFc7Z2/B+LZxZ48J QXNZSUb3z/Y8o2OBhilH0BhwcA+MNRBg8ngKSMYcyQG/Xw6OqlMHebJFSHMySzxDKC2E zx3JW8d6AAnHv2VvsApQ5wzzvebDWrerN1pnnudTqg6m4SaVjPCPe5U1M6yi+lZdAUck KvlA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@michaelkloos.com header.s=k1 header.b=Yx2elFfE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id oj15si2232629pjb.149.2022.01.24.02.28.49; Mon, 24 Jan 2022 02:29:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@michaelkloos.com header.s=k1 header.b=Yx2elFfE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238956AbiAWQxg (ORCPT + 99 others); Sun, 23 Jan 2022 11:53:36 -0500 Received: from m228-6.mailgun.net ([159.135.228.6]:50887 "EHLO m228-6.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238947AbiAWQxf (ORCPT ); Sun, 23 Jan 2022 11:53:35 -0500 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=michaelkloos.com; q=dns/txt; s=k1; t=1642956814; h=Content-Transfer-Encoding: Content-Type: In-Reply-To: From: References: Cc: To: Subject: MIME-Version: Date: Message-ID: Sender; bh=IHqd7yX1XGLLOu24CAliRnIh4Fy6X/3R/a7MUMsmKr8=; b=Yx2elFfEhNDd4sz+huIEXMySE0x4XHgOHg9q1kKo/EaSzgGK4j8gCRO91VZKargoay0XPngU YmQje69X27/O546uoPF5zQNtm6KpP8MC/jdTPYXjYFliGn032r2mIdsT+EaDIPkpEMd5X4tb t49bOaB4YNDJcraoRpRVrEGz5K8= X-Mailgun-Sending-Ip: 159.135.228.6 X-Mailgun-Sid: WyI5NjYzNiIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgIjQ4Y2MwIl0= Received: from drop1.michaelkloos.com (drop1.michaelkloos.com [67.205.190.89]) by smtp-out-n04.prod.us-west-2.postgun.com with SMTP id 61ed880d7e1ee9b1c1ae3a18 (version=TLS1.3, cipher=TLS_AES_128_GCM_SHA256); Sun, 23 Jan 2022 16:53:33 GMT Sender: michael@michaelkloos.com Received: from [192.168.0.104] (cpe-173-88-115-50.columbus.res.rr.com [173.88.115.50]) by drop1.michaelkloos.com (Postfix) with ESMTPSA id AD4AC40249; Sun, 23 Jan 2022 16:53:31 +0000 (UTC) Message-ID: Date: Sun, 23 Jan 2022 11:53:31 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH v2] Fixed: Misaligned memory access. Fixed pointer comparison. Content-Language: en-US To: David Laight , "paul.walmsley@sifive.com" , "palmer@dabbelt.com" , "aou@eecs.berkeley.edu" Cc: "linux-riscv@lists.infradead.org" , "linux-kernel@vger.kernel.org" References: <20220123034518.3717116-1-michael@michaelkloos.com> From: "Michael T. Kloos" In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org No. It only uses tabs. The previous version used spaces. Make sure that you are not looking at a line with a '-'. The only place that spaces, perhaps combined with tabs, appear at the start of a line in my patch is to align the '*' character for a multi-line comment. In this case, tab(s) are followed by a single space for alignment. I believe this is correct per the coding style. If I am wrong, please let me know. ----Michael On 1/23/22 08:31, David Laight wrote: > From: michael@michaelkloos.com >> Sent: 23 January 2022 03:45 >> >> Rewrote the riscv memmove() assembly implementation. The >> previous implementation did not check memory alignment and it >> compared 2 pointers with a signed comparison. The misaligned >> memory access would cause the kernel to crash on systems that >> did not emulate it in firmware and did not support it in hardware. >> Firmware emulation is slow and may not exist. Additionally, >> hardware support may not exist and would likely still run slower >> than aligned accesses even if it did. The RISC-V spec does not >> guarantee that support for misaligned memory accesses will exist. >> It should not be depended on. > ... > > From the way my email client display the patch I think it is > using both tabs and spaces for indentation. > > David > > - > Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK > Registration No: 1397386 (Wales) >