From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "rdunlap@infradead.org" <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "bwidawsk@kernel.org" <bwidawsk@kernel.org>,
"Schofield, Alison" <alison.schofield@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Weiny, Ira" <ira.weiny@intel.com>
Subject: Re: [PATCH v2] cxl: fix spelling mistakes
Date: Wed, 25 Jan 2023 18:50:10 +0000 [thread overview]
Message-ID: <e8d5e120f78a34b255173f34d0955cee385a6974.camel@intel.com> (raw)
In-Reply-To: <20230125032221.21277-1-rdunlap@infradead.org>
On Tue, 2023-01-24 at 19:22 -0800, Randy Dunlap wrote:
> Correct spelling mistakes (reported by codespell).
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Alison Schofield <alison.schofield@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Cc: Ben Widawsky <bwidawsk@kernel.org>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: linux-cxl@vger.kernel.org
> ---
> v2: add corrections for other source-code spelling errors (Alison)
>
> drivers/cxl/Kconfig | 2 +-
> drivers/cxl/acpi.c | 2 +-
> drivers/cxl/core/port.c | 2 +-
> drivers/cxl/core/region.c | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
Looks good,
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
>
> diff -- a/drivers/cxl/Kconfig b/drivers/cxl/Kconfig
> --- a/drivers/cxl/Kconfig
> +++ b/drivers/cxl/Kconfig
> @@ -116,7 +116,7 @@ config CXL_REGION_INVALIDATION_TEST
> depends on CXL_REGION
> help
> CXL Region management and security operations potentially invalidate
> - the content of CPU caches without notifiying those caches to
> + the content of CPU caches without notifying those caches to
> invalidate the affected cachelines. The CXL Region driver attempts
> to invalidate caches when those events occur. If that invalidation
> fails the region will fail to enable. Reasons for cache
> diff -- a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
> --- a/drivers/cxl/acpi.c
> +++ b/drivers/cxl/acpi.c
> @@ -19,7 +19,7 @@ struct cxl_cxims_data {
>
> /*
> * Find a targets entry (n) in the host bridge interleave list.
> - * CXL Specfication 3.0 Table 9-22
> + * CXL Specification 3.0 Table 9-22
> */
> static int cxl_xor_calc_n(u64 hpa, struct cxl_cxims_data *cximsd, int iw,
> int ig)
> diff -- a/drivers/cxl/core/port.c b/drivers/cxl/core/port.c
> --- a/drivers/cxl/core/port.c
> +++ b/drivers/cxl/core/port.c
> @@ -1137,7 +1137,7 @@ static struct cxl_port *find_cxl_port_at
> }
>
> /*
> - * All users of grandparent() are using it to walk PCIe-like swich port
> + * All users of grandparent() are using it to walk PCIe-like switch port
> * hierarchy. A PCIe switch is comprised of a bridge device representing the
> * upstream switch port and N bridges representing downstream switch ports. When
> * bridges stack the grand-parent of a downstream switch port is another
> diff -- a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -399,7 +399,7 @@ static ssize_t interleave_granularity_st
> * When the host-bridge is interleaved, disallow region granularity !=
> * root granularity. Regions with a granularity less than the root
> * interleave result in needing multiple endpoints to support a single
> - * slot in the interleave (possible to suport in the future). Regions
> + * slot in the interleave (possible to support in the future). Regions
> * with a granularity greater than the root interleave result in invalid
> * DPA translations (invalid to support).
> */
next prev parent reply other threads:[~2023-01-25 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 3:22 [PATCH v2] cxl: fix spelling mistakes Randy Dunlap
2023-01-25 15:53 ` Alison Schofield
2023-01-25 18:50 ` Verma, Vishal L [this message]
2023-01-26 23:56 ` Dan Williams
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=e8d5e120f78a34b255173f34d0955cee385a6974.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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