From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (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 99E1A25DAE3; Mon, 24 Mar 2025 09:11:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1742807505; cv=none; b=bOdjXPm6J4zRGSe9WN89xZzX9wm6f/ezPTgjRaGLJHc/CqqvwGPdlmSDAjeafv+NqWJp9bRFtK20VnQ1QI+w+OiwfSLcEhT3ppG7DazzXYzfRAlRg6G/cGv9mlBPl4ra1nSALPkOAslXxdk65Pv3+0+V9bcr2H2AwvTEGqjunDY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1742807505; c=relaxed/simple; bh=xtSXh6+Zee/Qft/ZxFihJqkWvvhc0WQOhGMs9uEvn2g=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=lDPkY0htH7Are60DnyDXNVD97j/L49JiRJZADQlWaRz3vNGwOzymmWSq5B7rGQk6l7ZKJxeu+/aBGwp1poORsXOz68DGDnbPmJLt2WFFicnjNCGShFyGjMyTLQy20pEsQYWpH5qvxvM8hNA2AbrmWkPBBGKAX5KP/j+x1dEr6zk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=FIdz+bY9; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="FIdz+bY9" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=ClmexxLxtozHEJVd1kpHjy+FBvc2bx8jEjpjkQaesy0=; t=1742807503; x=1744017103; b=FIdz+bY9YVYWs87kGsN8m6+Dzbl2uoaQzuqS4CHBlq0I+Ee PnX0OlKV8szjS6h50YiI6Eln0xodcIzfw2bEUQBWbY4nVgnAfjivnmM42R5ilhB+mk3rkaSHZ2m3s EmEhBzw+Srxa+fg46+DQANB6Sp6qqTKYULBzXOAzSEr0+1nCfyq1yGEsQmfKvieKvzMcvLq7VjslD rX9Cc0XcMUYeJubsXaA4NwraXJE3zAMjvCuBPQr08wSfoSL3bc905wVrlFM4vruph6jD8flPqVeql p9AdCnUn4JV+AuFHcvQ3sbTuSxuwduby088LgKn2+mbWA4rYxJk96kOp+Ejw9Dmw==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98) (envelope-from ) id 1twdqH-00000003u77-0qg7; Mon, 24 Mar 2025 10:11:33 +0100 Message-ID: Subject: Re: [PATCH wireless] wifi: iwlwifi:: fix spelling errors From: Johannes Berg To: Wang Liang , miriam.rachel.korenblit@intel.com, ganjie182@gmail.com, emmanuel.grumbach@intel.com, avraham.stern@intel.com Cc: yuehaibing@huawei.com, zhangchangzhong@huawei.com, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Date: Mon, 24 Mar 2025 10:11:31 +0100 In-Reply-To: <20250324030021.2296493-1-wangliang74@huawei.com> References: <20250324030021.2296493-1-wangliang74@huawei.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Mon, 2025-03-24 at 11:00 +0800, Wang Liang wrote: > Fix some spelling errors in comments: > - configuraiton -> configuration > - notificaiton -> notification >=20 > No functional changes. >=20 FWIW, spelling errors really don't need to be fixed on wireless, that can wait for wireless-next. johannes