From: patchwork-bot+linux-riscv@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: linux-riscv@lists.infradead.org, arnd@arndb.de,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-snps-arc@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-hexagon@vger.kernel.org, loongarch@lists.linux.dev,
linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org,
linux-openrisc@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org,
linux-um@lists.infradead.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] asm-generic: provide generic page_to_phys and phys_to_page implementations
Date: Wed, 11 Dec 2024 22:32:44 +0000 [thread overview]
Message-ID: <173395636448.1729195.13128530873311699126.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241023053644.311692-2-hch@lst.de>
Hello:
This series was applied to riscv/linux.git (fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 23 Oct 2024 07:36:36 +0200 you wrote:
> page_to_phys is duplicated by all architectures, and from some strange
> reason placed in <asm/io.h> where it doesn't fit at all.
>
> phys_to_page is only provided by a few architectures despite having a lot
> of open coded users.
>
> Provide generic versions in <asm-generic/memory_model.h> to make these
> helpers more easily usable.
>
> [...]
Here is the summary with links:
- [1/2] asm-generic: provide generic page_to_phys and phys_to_page implementations
https://git.kernel.org/riscv/c/c5c3238d9b8c
- [2/2] asm-generic: add an optional pfn_valid check to page_to_phys
https://git.kernel.org/riscv/c/3e25d5a49f99
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-12-11 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 5:36 provide generic page_to_phys and phys_to_page implementations v3 Christoph Hellwig
2024-10-23 5:36 ` [PATCH 1/2] asm-generic: provide generic page_to_phys and phys_to_page implementations Christoph Hellwig
2024-12-11 22:32 ` patchwork-bot+linux-riscv [this message]
2024-10-23 5:36 ` [PATCH 2/2] asm-generic: add an optional pfn_valid check to page_to_phys Christoph Hellwig
2024-11-05 9:56 ` Christophe Leroy
2024-10-25 13:37 ` provide generic page_to_phys and phys_to_page implementations v3 Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2024-10-14 14:44 provide generic page_to_phys and phys_to_page implementations v2 Christoph Hellwig
2024-10-14 14:44 ` [PATCH 1/2] asm-generic: provide generic page_to_phys and phys_to_page implementations Christoph Hellwig
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=173395636448.1729195.13128530873311699126.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=sparclinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).