From nobody Fri Jun 12 21:39:56 2026 Received: from cvsmtppost07.nm.naver.com (cvsmtppost07.nm.naver.com [114.111.35.153]) (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 E8C862417DE for ; Tue, 12 May 2026 14:45:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=114.111.35.153 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778597156; cv=none; b=AoMr2A4djPSTsR15MhG4KpOlata1Nb8h4qQYm5DquTO7QikFteDWASYIlKCFQRKzrNY/yMusGov1tn8pYslUseV6NUuQKt7gDtRRlralm46m+BI6a0l3nVCc75giifdM6krcQ0Zc1crMEyy+a7IWELXi3utnl2FYAheqOk8WZG0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778597156; c=relaxed/simple; bh=L76w+ouDkw8KYqvjRGLBKNLlN0zpsQMNQulS8XZCbK8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Tn6tw07MXfmkgAyj5tXKdFd5R+qYBWvBL2IfytA8SGD+yKAzXZCnwhcbcdler3VG2alC0xbL8K1tXjUpqsA0Ed9fdaET8s594brXfakHYLb7c2Dua1U8gD1+BmuGZzQOReYtPQcSMQmz+7K6l4uQHs8ItEBtwhdCPgFdgDnqBOw= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=naver.com; spf=pass smtp.mailfrom=naver.com; dkim=pass (2048-bit key) header.d=naver.com header.i=@naver.com header.b=E88gBDzO; arc=none smtp.client-ip=114.111.35.153 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=naver.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=naver.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=naver.com header.i=@naver.com header.b="E88gBDzO" Received: from cvsendbo021.nm ([10.112.18.58]) by cvsmtppost07.nm.naver.com with ESMTP id B6-blem5RaWOrh2G60q5FA for ; Tue, 12 May 2026 14:35:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=naver.com; s=s20171208; t=1778596546; bh=L76w+ouDkw8KYqvjRGLBKNLlN0zpsQMNQulS8XZCbK8=; h=From:To:Subject:Date:Message-ID:From:Subject:Feedback-ID: X-Works-Security; b=E88gBDzOdN7NOnLbUwRzFgYq3TakG9Mh6VkE2/xd0Hl9nQMYH1LivpmqxFjvsewUI 1IzbKgK0N5xw/w0RIB879VDUtdGQxaq4B90OG5wk2G7ifcEXAjmxljddkcTiu8oOjA QdU7uXqVL85YluZfK5oALfNtdhIN/MPCbRFNZJKuGJQusCZZRIbuTpotpQc5v76zUy itNVtvKNkBMZsEIIyLGnQbnkF7Ce/RsnYVCgQYftlXJ60Nupsc3oPv67dfGNxvYGbh /Whqb3xUNJjj22HbU0+a7yH2iIiCxveqcrsPe4vP2B6td09nsc+KZ+N5iBxH5oO6AY K25GLUldEafvw== X-Session-ID: rkY7GxkhQYavHSniVnx2YA X-Works-Send-Opt: LdYwjAJYjHmZaAKqKBmmKxbwKqpYkEljxBmwjAg= X-Works-Smtp-Source: VZnrFx2XFqJZ+Hm9FAud+6E= Received: from JMW-Ubuntu.. ([14.38.141.199]) by cvnsmtp009.nm.naver.com with ESMTP id rkY7GxkhQYavHSniVnx2YA for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Tue, 12 May 2026 14:35:45 -0000 From: Minu Jin To: akpm@linux-foundation.org, david@kernel.org Cc: ljs@kernel.org, liam@infradead.org, vbabka@kernel.org, rppt@kernel.org, surenb@google.com, mhocko@suse.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Minu Jin Subject: [PATCH] mm: fix misleading comment for remap_pfn_range() Date: Tue, 12 May 2026 23:35:43 +0900 Message-ID: <20260512143543.258399-1-s9430939@naver.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The function summary describes this as remapping "kernel memory", but remap_pfn_range() operates on arbitrary PFNs, including device MMIO regions that are not kernel memory at all. Replace with "physical address range". It describes accurately what the function maps. Signed-off-by: Minu Jin --- mm/memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/memory.c b/mm/memory.c index ea6568571131..4e07e03a76a4 100644 --- a/mm/memory.c +++ b/mm/memory.c @@ -3172,7 +3172,7 @@ static int remap_pfn_range_prepare_vma(struct vm_area= _struct *vma, } =20 /** - * remap_pfn_range - remap kernel memory to userspace + * remap_pfn_range - remap physical address range to user space * @vma: user vma to map to * @addr: target page aligned user address to start at * @pfn: page frame number of kernel physical memory address --=20 2.43.0