From: Jason Gunthorpe <jgg@nvidia.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
linuxppc-dev@lists.ozlabs.org,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Kevin Tian <kevin.tian@intel.com>,
kernel test robot <lkp@intel.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
patches@lists.linux.dev, Vasant Hegde <vasant.hegde@amd.com>
Subject: Re: [PATCH] powerpc/pseries/svm: Make mem_encrypt.h self contained
Date: Thu, 20 Nov 2025 12:40:53 -0400 [thread overview]
Message-ID: <20251120164053.GD153257@nvidia.com> (raw)
In-Reply-To: <0951c9b6-4252-46e5-a260-0e42365c5018@csgroup.eu>
On Thu, Nov 20, 2025 at 04:09:14PM +0100, Christophe Leroy wrote:
> > diff --git a/arch/powerpc/include/asm/mem_encrypt.h b/arch/powerpc/include/asm/mem_encrypt.h
> > index 2f26b8fc8d297c..e355ca46fad933 100644
> > --- a/arch/powerpc/include/asm/mem_encrypt.h
> > +++ b/arch/powerpc/include/asm/mem_encrypt.h
> > @@ -9,6 +9,9 @@
> > #define _ASM_POWERPC_MEM_ENCRYPT_H
> > #include <asm/svm.h>
> > +#include <linux/types.h>
>
> Why do you need linux/types.h ? Isn't the below forward declaration enough ?
For bool:
> > +
> > +struct device;
> > static inline bool force_dma_unencrypted(struct device *dev)
^^^^^^
Jason
prev parent reply other threads:[~2025-11-20 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 15:06 [PATCH] powerpc/pseries/svm: Make mem_encrypt.h self contained Jason Gunthorpe
2025-11-20 15:09 ` Christophe Leroy
2025-11-20 16:40 ` Jason Gunthorpe [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=20251120164053.GD153257@nvidia.com \
--to=jgg@nvidia.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=christophe.leroy@csgroup.eu \
--cc=joerg.roedel@amd.com \
--cc=kevin.tian@intel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=pasha.tatashin@soleen.com \
--cc=patches@lists.linux.dev \
--cc=vasant.hegde@amd.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;
as well as URLs for NNTP newsgroup(s).