From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 773CA377556 for ; Tue, 17 Feb 2026 21:12:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771362760; cv=none; b=iZA/OQnF8VTCtbR7F1/gxGQ+kFpgTzvMcyQbODt+mxl1Mms0j3c8qH1MlbIhn+5tCT5Q1aqRWKQbrJzm+A2SoGLqI/gugBkLBQuagj8+1SEznlMf9pBv7NGYv2W6gTSNkFgzMzyDLhnHdxSsYsAIiwu7Gd4DRR0SDJECC1txw6o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771362760; c=relaxed/simple; bh=p9Cuh7jV01riqByEHWOnkwIMeAOedx6kRn+SkqSMcMY=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=X1xZdcY41oIPj8RxuMnPkY+y1W7ei7sWwyojdVcpuSlhQptYG1y9z7cjX2kIJ3C08oKPeKH0oeReTKnEBXm6cfGr+OszZX3ErduL9wHaFztTJc4VD9svNHKqYFsChLDHk9SfuP0lFi57jMghgN2bdgaPv76osf+shzACiW9+Tts= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hs9/BSWA; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="hs9/BSWA" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 13A6AC19421; Tue, 17 Feb 2026 21:12:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771362760; bh=p9Cuh7jV01riqByEHWOnkwIMeAOedx6kRn+SkqSMcMY=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=hs9/BSWAHzwxVmMyCDjF6xO5O9TsZxZ5Ib++0vwwExcm0EbE8HnAXmvd8sECLjsbq IJM9iB8DBybkybl4zh8jC6sKL6BZn8uB+32YmqxcBlpPWoNplgRLZUSluMONtcJIpJ OZshfquItwitekWM7L4zWbnhzoVLf0guaWbTn16cqQPGBvLB1/SZMd4RO/EMxZQRWR jesFUGjV8qlJJqws1JICzMfWDw+oFCgbZTpc2A6J+uVDaO7PLZ2A1w2Zi5A4q8o1WL u9gllsJ7QLy9fUMJ1jGOC4TaqfH2mUGpPB4/olGc4FrRYYSm/z44jQcmvtpgo4IjY5 XXNOoULni+zRA== Date: Tue, 17 Feb 2026 14:12:36 -0700 (MST) From: Paul Walmsley To: Kunwu Chan , igor.b@beldev.am cc: namcao@linutronix.de, Paul Walmsley , Palmer Dabbelt , Albert Ou , Conor Dooley , Alexandre Ghiti , Anup Patel , Atish Patra , Zong Li , Deepak Gupta , Zhouyi Zhou , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND 0/2] riscv: fix minor typos and style issues in XIP code In-Reply-To: <20260214023804.677127-1-kunwu.chan@linux.dev> Message-ID: <609b889a-8bb1-d2b5-8de6-ddeec27cac04@kernel.org> References: <20260214023804.677127-1-kunwu.chan@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII On Sat, 14 Feb 2026, Kunwu Chan wrote: > Fix a few minor issues found in riscv XIP-related code: > > - xip_fixup.h: comment typo (_start vs _sdata) and spaces-vs-tab > - head.S: spelling typo and wrong #endif comment Thanks for fixing the threading, but, Conor's message: https://lore.kernel.org/linux-riscv/20260213-canteen-diffuser-5ecc80f264b4@spud/ was exactly right. Folks who care about XIP support for RISC-V first need to send patches to fix it in mainline. These typo fixes should be rolled in to that series. Until that happens, I plan to keep the XIP removal patches queued. I also want to see the XIP folks participating in testing and reviewing upstream patches going forward to confirm that they don't break XIP support. Otherwise, the burden is just getting pushed to patch submitters and maintainers, most of whom probably don't care much about XIP. And there's a good chance that we'll just go through this cycle again in another few months. - Paul