From: kernel test robot <lkp@intel.com>
To: Mohamad Raizudeen <raizudeen.kerneldev@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: drivers/crypto/amlogic/amlogic-gxl-core.c:166:42: error: implicit declaration of function 'devm_crypto_engine_alloc_init'; did you mean 'crypto_engine_alloc_init'?
Date: Mon, 31 Aug 2026 03:28:10 +0200 [thread overview]
Message-ID: <202608310329.QgxCCMs1-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Mohamad-Raizudeen/crypto-amlogic-Use-devm-APIs-for-clock-and-engine-management/20260821-204303
head: 9f703793f0a723cf495c90aed76fb7f1e99e02b1
commit: 9f703793f0a723cf495c90aed76fb7f1e99e02b1 crypto: amlogic: Use devm APIs for clock and engine management
date: 8 days ago
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260831/202608310329.QgxCCMs1-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260831/202608310329.QgxCCMs1-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/202608310329.QgxCCMs1-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/crypto/amlogic/amlogic-gxl-core.c: In function 'meson_allocate_chanlist':
>> drivers/crypto/amlogic/amlogic-gxl-core.c:166:42: error: implicit declaration of function 'devm_crypto_engine_alloc_init'; did you mean 'crypto_engine_alloc_init'? [-Wimplicit-function-declaration]
166 | mc->chanlist[i].engine = devm_crypto_engine_alloc_init(mc->dev, true);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| crypto_engine_alloc_init
>> drivers/crypto/amlogic/amlogic-gxl-core.c:166:40: error: assignment to 'struct crypto_engine *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
166 | mc->chanlist[i].engine = devm_crypto_engine_alloc_init(mc->dev, true);
| ^
vim +166 drivers/crypto/amlogic/amlogic-gxl-core.c
150
151 /*
152 * Allocate the channel list structure
153 */
154 static int meson_allocate_chanlist(struct meson_dev *mc)
155 {
156 int i, err;
157
158 mc->chanlist = devm_kcalloc(mc->dev, MAXFLOW,
159 sizeof(struct meson_flow), GFP_KERNEL);
160 if (!mc->chanlist)
161 return -ENOMEM;
162
163 for (i = 0; i < MAXFLOW; i++) {
164 init_completion(&mc->chanlist[i].complete);
165
> 166 mc->chanlist[i].engine = devm_crypto_engine_alloc_init(mc->dev, true);
167 if (!mc->chanlist[i].engine) {
168 dev_err(mc->dev, "Cannot allocate engine\n");
169 i--;
170 err = -ENOMEM;
171 goto error_engine;
172 }
173 err = crypto_engine_start(mc->chanlist[i].engine);
174 if (err) {
175 dev_err(mc->dev, "Cannot start engine\n");
176 goto error_engine;
177 }
178 mc->chanlist[i].tl = dma_alloc_coherent(mc->dev,
179 sizeof(struct meson_desc) * MAXDESC,
180 &mc->chanlist[i].t_phy,
181 GFP_KERNEL);
182 if (!mc->chanlist[i].tl) {
183 err = -ENOMEM;
184 goto error_engine;
185 }
186 }
187 return 0;
188 error_engine:
189 meson_free_chanlist(mc, i);
190 return err;
191 }
192
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-31 1:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608310329.QgxCCMs1-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raizudeen.kerneldev@gmail.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 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.