From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
sstabellini@kernel.org, linux@armlinux.org.uk,
xen-devel@lists.xenproject.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] ARM: xen/mm.c: A mundane typo fix
Date: Wed, 24 Mar 2021 16:48:26 -0700 [thread overview]
Message-ID: <e3980acb-e6d7-645a-3be0-79cea6f2fd8e@infradead.org> (raw)
In-Reply-To: <20210325043526.16289-1-unixbhaskar@gmail.com>
On 3/24/21 9:35 PM, Bhaskar Chowdhury wrote:
> s/acrros/across/
>
> Plus some words need prural version...so did it.(page->pages)
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Changes from V1:
> Randy's findings incorporated.
>
> arch/arm/xen/mm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/xen/mm.c b/arch/arm/xen/mm.c
> index 467fa225c3d0..8596dd32dcd5 100644
> --- a/arch/arm/xen/mm.c
> +++ b/arch/arm/xen/mm.c
> @@ -105,8 +105,8 @@ bool xen_arch_need_swiotlb(struct device *dev,
> * - The Linux page refers to foreign memory
> * - The device doesn't support coherent DMA request
> *
> - * The Linux page may be spanned acrros multiple Xen page, although
> - * it's not possible to have a mix of local and foreign Xen page.
> + * The Linux page may be spanned across multiple Xen pages, although
> + * it's not possible to have a mix of local and foreign Xen pages.
> * Furthermore, range_straddles_page_boundary is already checking
> * if buffer is physically contiguous in the host RAM.
> *
> --
--
~Randy
next prev parent reply other threads:[~2021-03-24 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 4:35 Bhaskar Chowdhury
2021-03-24 23:48 ` Randy Dunlap [this message]
2021-03-25 15:22 ` Stefano Stabellini
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=e3980acb-e6d7-645a-3be0-79cea6f2fd8e@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sstabellini@kernel.org \
--cc=unixbhaskar@gmail.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®