From: kernel test robot <lkp@intel.com>
To: "Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-coco@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
will@kernel.org, robin.murphy@arm.com, suzuki.poulose@arm.com,
jgg@ziepe.ca, steven.price@arm.com,
Marek Szyprowski <m.szyprowski@samsung.com>,
"Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>
Subject: Re: [PATCH 2/2] dma-direct: Make phys_to_dma() pick encrypted vs unencrypted per device
Date: Tue, 20 Jan 2026 18:49:27 +0800 [thread overview]
Message-ID: <202601201857.7LKBY5dB-lkp@intel.com> (raw)
In-Reply-To: <20260120064255.179425-2-aneesh.kumar@kernel.org>
Hi Aneesh,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.19-rc6 next-20260119]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Aneesh-Kumar-K-V-Arm/dma-direct-Make-phys_to_dma-pick-encrypted-vs-unencrypted-per-device/20260120-145025
base: linus/master
patch link: https://lore.kernel.org/r/20260120064255.179425-2-aneesh.kumar%40kernel.org
patch subject: [PATCH 2/2] dma-direct: Make phys_to_dma() pick encrypted vs unencrypted per device
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20260120/202601201857.7LKBY5dB-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601201857.7LKBY5dB-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601201857.7LKBY5dB-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/dma/direct.h:10,
from kernel/dma/mapping.c:19:
include/linux/dma-direct.h: In function 'phys_to_dma':
>> include/linux/dma-direct.h:103:13: error: implicit declaration of function 'force_dma_unencrypted'; did you mean 'phys_to_dma_unencrypted'? [-Wimplicit-function-declaration]
103 | if (force_dma_unencrypted(dev))
| ^~~~~~~~~~~~~~~~~~~~~
| phys_to_dma_unencrypted
include/linux/dma-direct.h: At top level:
>> include/linux/dma-direct.h:125:20: error: conflicting types for 'force_dma_unencrypted'; have 'bool(struct device *)' {aka '_Bool(struct device *)'}
125 | static inline bool force_dma_unencrypted(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/dma-direct.h:103:13: note: previous implicit declaration of 'force_dma_unencrypted' with type 'int()'
103 | if (force_dma_unencrypted(dev))
| ^~~~~~~~~~~~~~~~~~~~~
vim +103 include/linux/dma-direct.h
102
> 103 if (force_dma_unencrypted(dev))
104 return phys_to_dma_unencrypted(dev, paddr);
105 return phys_to_dma_encrypted(dev, paddr);
106 }
107
108 static inline phys_addr_t dma_to_phys(struct device *dev, dma_addr_t dma_addr)
109 {
110 phys_addr_t paddr;
111
112 dma_addr = dma_addr_canonical(dma_addr);
113 if (dev->dma_range_map)
114 paddr = translate_dma_to_phys(dev, dma_addr);
115 else
116 paddr = dma_addr;
117
118 return paddr;
119 }
120 #endif /* !CONFIG_ARCH_HAS_PHYS_TO_DMA */
121
122 #ifdef CONFIG_ARCH_HAS_FORCE_DMA_UNENCRYPTED
123 bool force_dma_unencrypted(struct device *dev);
124 #else
> 125 static inline bool force_dma_unencrypted(struct device *dev)
126 {
127 return false;
128 }
129 #endif /* CONFIG_ARCH_HAS_FORCE_DMA_UNENCRYPTED */
130
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-20 10:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 6:42 [PATCH 1/2] dma-direct: Validate DMA mask against canonical DMA addresses Aneesh Kumar K.V (Arm)
2026-01-20 6:42 ` [PATCH 2/2] dma-direct: Make phys_to_dma() pick encrypted vs unencrypted per device Aneesh Kumar K.V (Arm)
2026-01-20 9:33 ` kernel test robot
2026-01-20 10:49 ` kernel test robot [this message]
2026-01-20 9:59 ` [PATCH 1/2] dma-direct: Validate DMA mask against canonical DMA addresses Suzuki K Poulose
2026-01-20 11:59 ` Robin Murphy
2026-01-20 14:25 ` Aneesh Kumar K.V
2026-01-20 19:22 ` Robin Murphy
2026-01-21 4:50 ` Aneesh Kumar K.V
2026-01-20 14:18 ` Aneesh Kumar K.V
2026-01-20 14:39 ` Suzuki K Poulose
2026-01-20 15:11 ` Jason Gunthorpe
2026-01-20 17:11 ` Robin Murphy
2026-01-20 17:54 ` Jason Gunthorpe
2026-01-20 18:47 ` Robin Murphy
2026-01-20 19:54 ` Jason Gunthorpe
2026-01-20 10:59 ` kernel test robot
2026-01-20 13:26 ` Jason Gunthorpe
2026-01-20 15:25 ` Aneesh Kumar K.V
2026-01-20 15:43 ` Jason Gunthorpe
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=202601201857.7LKBY5dB-lkp@intel.com \
--to=lkp@intel.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.