linux-kernel - [PATCH] platform/x86/intel/pmt: Correct the typo 'ACCCESS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <781C12799421D366+20240920031620.1211752-1-wangyuli@uniontech.com>
Date: Fri, 20 Sep 2024 11:16:20 +0800
From: WangYuli <wangyuli@...ontech.com>
To: david.e.box@...ux.intel.com,
	hdegoede@...hat.com,
	ilpo.jarvinen@...ux.intel.com
Cc: platform-driver-x86@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	tzimmermann@...e.de,
	lee.jones@...aro.org,
	lee@...nel.org,
	guanwentao@...ontech.com,
	zhanjun@...ontech.com,
	WangYuli <wangyuli@...ontech.com>
Subject: [PATCH] platform/x86/intel/pmt: Correct the typo 'ACCCESS_LOCAL'

There is a spelling mistake of 'ACCCESS_LOCAL' which should be
instead of 'ACCESS_LOCAL'.

Cc: Thomas Zimmermann <tzimmermann@...e.de>
Signed-off-by: WangYuli <wangyuli@...ontech.com>
---
 drivers/platform/x86/intel/pmt/class.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/platform/x86/intel/pmt/class.c b/drivers/platform/x86/intel/pmt/class.c
index c04bb7f97a4d..7680474c4f96 100644
--- a/drivers/platform/x86/intel/pmt/class.c
+++ b/drivers/platform/x86/intel/pmt/class.c
@@ -207,7 +207,7 @@ static int intel_pmt_populate_entry(struct intel_pmt_entry *entry,
 		/*
 		 * Some hardware use a different calculation for the base address
 		 * when access_type == ACCESS_LOCAL. On the these systems
-		 * ACCCESS_LOCAL refers to an address in the same BAR as the
+		 * ACCESS_LOCAL refers to an address in the same BAR as the
 		 * header but at a fixed offset. But as the header address was
 		 * supplied to the driver, we don't know which BAR it was in.
 		 * So search for the bar whose range includes the header address.
-- 
2.45.2