From: Linus Walleij <linus.walleij@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>, Vineet Gupta <vgupta@kernel.org>,
Brian Cain <bcain@quicinc.com>
Cc: linux-arch@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hexagon@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 0/2] arch: Virt to phys to static inlines
Date: Wed, 15 Nov 2023 14:28:13 +0100 [thread overview]
Message-ID: <20231115-virt-to-phy-arch-tree-v1-0-8b61296eae73@linaro.org> (raw)
Some architectures have been given patches to switch their
virt_to_phys()/phys_to_virt() or underlying *pfn etc functions
over to static inlines.
Some patches have been ignored or have no maintained arch
tree.
This set includes patches that I suggest to simply be applied
to the arch tree so they get in.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Linus Walleij (2):
ARC: mm: Make virt_to_pfn() a static inline
Hexagon: Make pfn accessors statics inlines
arch/arc/include/asm/page.h | 21 ++++++++++++---------
arch/arc/include/asm/pgtable-levels.h | 2 +-
arch/hexagon/include/asm/page.h | 15 +++++++++++++--
3 files changed, 26 insertions(+), 12 deletions(-)
---
base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
change-id: 20231115-virt-to-phy-arch-tree-137bc87046e1
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next reply other threads:[~2023-11-15 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 13:28 Linus Walleij [this message]
2023-11-15 13:28 ` [PATCH 1/2] ARC: mm: Make virt_to_pfn() a static inline Linus Walleij
2023-11-15 13:28 ` [PATCH 2/2] Hexagon: Make pfn accessors statics inlines Linus Walleij
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=20231115-virt-to-phy-arch-tree-v1-0-8b61296eae73@linaro.org \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=bcain@quicinc.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vgupta@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 read-only IMAP folder(s) and NNTP newsgroup(s).