From: Heiko Carstens <hca@linux.ibm.com>
To: "T.J. Mercier" <tjmercier@google.com>
Cc: agordeev@linux.ibm.com, gerald.schaefer@linux.ibm.com,
linux-s390@vger.kernel.org, mripard@kernel.org,
sumit.semwal@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/mm: Export set_memory_encrypted and set_memory_decrypted
Date: Sat, 23 May 2026 18:01:31 +0200 [thread overview]
Message-ID: <20260523160131.11676Ac3-hca@linux.ibm.com> (raw)
In-Reply-To: <20260522230606.883180-1-tjmercier@google.com>
On Fri, May 22, 2026 at 04:06:05PM -0700, T.J. Mercier wrote:
> After commit fd55edff8a0a ("dma-buf: heaps: system: Turn the heap into a
> module") the system dma-buf heaps can be built as a module. The
> system_cc_shared heap uses set_memory_encrypted and set_memory_decrypted
> but those functions are not exported on s390. This results in a build
> error like:
>
> >> ERROR: modpost: "set_memory_decrypted" [drivers/dma-buf/heaps/system_heap.ko] undefined!
> >> ERROR: modpost: "set_memory_encrypted" [drivers/dma-buf/heaps/system_heap.ko] undefined!
>
> Export the functions so system_heap.ko can be built.
>
> Fixes: fd55edff8a0a ("dma-buf: heaps: system: Turn the heap into a module")
> Signed-off-by: T.J. Mercier <tjmercier@google.com>
> ---
> arch/s390/mm/init.c | 2 ++
> 1 file changed, 2 insertions(+)
Fine with me, but this should go via drm-misc-next, since the commit
which breaks this is currently only available in linux-next.
Sumit, I guess you will add this to your queue?
In any case:
Acked-by: Heiko Carstens <hca@linux.ibm.com>
prev parent reply other threads:[~2026-05-23 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 23:06 [PATCH] s390/mm: Export set_memory_encrypted and set_memory_decrypted T.J. Mercier
2026-05-23 16:01 ` Heiko Carstens [this message]
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=20260523160131.11676Ac3-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
/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