From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Sohil Mehta" <sohil.mehta@intel.com>,
"Tiezhu Yang" <yangtiezhu@loongson.cn>
Subject: Re: [GIT PULL] asm-generic updates for 6.5
Date: Thu, 06 Jul 2023 11:30:15 +0200 [thread overview]
Message-ID: <245a1e0d-197b-4ee0-985d-5c91a90e2a65@app.fastmail.com> (raw)
In-Reply-To: <9a23db59-1f53-4a24-87d7-a59293972a29@app.fastmail.com>
On Thu, Jul 6, 2023, at 10:20, Arnd Bergmann wrote:
> - A cleanup for virt_to_pfn/virt_to_bus to have proper type
> checking, forcing the use of pointers
Sorry, I meant to mention a conflict against f5f82cd18732
("Move netfs_extract_iter_to_sg() to lib/scatterlist.c"), which
Stephen fixed up in linux-next as below.
Arnd
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 9 Jun 2023 10:35:56 +1000
Subject: [PATCH] fix up for "Move netfs_extract_iter_to_sg() to lib/scatterlist.c"
interacting with "netfs: Pass a pointer to virt_to_page()"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
lib/scatterlist.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/scatterlist.c b/lib/scatterlist.c
index e97d7060329e..e86231a44c3d 100644
--- a/lib/scatterlist.c
+++ b/lib/scatterlist.c
@@ -1237,7 +1237,7 @@ static ssize_t extract_kvec_to_sg(struct iov_iter *iter,
if (is_vmalloc_or_module_addr((void *)kaddr))
page = vmalloc_to_page((void *)kaddr);
else
- page = virt_to_page(kaddr);
+ page = virt_to_page((void *)kaddr);
sg_set_page(sg, page, len, off);
sgtable->nents++;
next prev parent reply other threads:[~2023-07-06 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 8:20 Arnd Bergmann
2023-07-06 9:30 ` Arnd Bergmann [this message]
2023-07-06 17:28 ` pr-tracker-bot
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=245a1e0d-197b-4ee0-985d-5c91a90e2a65@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sohil.mehta@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yangtiezhu@loongson.cn \
/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®