From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: david.e.box@linux.intel.com, Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
tzimmermann@suse.de, lee.jones@linaro.org, lee@kernel.org,
guanwentao@uniontech.com, zhanjun@uniontech.com
Subject: Re: [PATCH] platform/x86/intel/pmt: Correct the typo 'ACCCESS_LOCAL'
Date: Fri, 20 Sep 2024 13:34:23 +0300 (EEST) [thread overview]
Message-ID: <26b8f38f-ff32-81fb-bbe5-aa141239427e@linux.intel.com> (raw)
In-Reply-To: <781C12799421D366+20240920031620.1211752-1-wangyuli@uniontech.com>
On Fri, 20 Sep 2024, WangYuli wrote:
> There is a spelling mistake of 'ACCCESS_LOCAL' which should be
> instead of 'ACCESS_LOCAL'.
"instead of ACCESS_LOCAL" means opposite of what you intended. I'd just
drop "instead of".
> Cc: Thomas Zimmermann <tzimmermann@suse.de>
> Signed-off-by: WangYuli <wangyuli@uniontech.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
The change is fine.
--
i.
prev parent reply other threads:[~2024-09-20 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 3:16 WangYuli
2024-09-20 10:34 ` Ilpo Järvinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26b8f38f-ff32-81fb-bbe5-aa141239427e@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=guanwentao@uniontech.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome