All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Harsh Jain <h.jain@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, Herbert Xu <herbert@gondor.apana.org.au>
Subject: [linux-next:master 9228/9539] drivers/crypto/xilinx/zynqmp-aes-gcm.c:556 xilinx_aes_aead_remove() warn: inconsistent indenting
Date: Sun, 25 Jan 2026 19:50:27 +0800	[thread overview]
Message-ID: <202601251908.baMDVVgW-lkp@intel.com> (raw)

Hi Harsh,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ca3a02fda4da8e2c1cb6baee5d72352e9e2cfaea
commit: 56934489a80a74a067d9129f025c81d1ebf267a4 [9228/9539] crypto: xilinx - Replace zynqmp prefix with xilinx
config: mips-randconfig-r071-20260125 (https://download.01.org/0day-ci/archive/20260125/202601251908.baMDVVgW-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 15.2.0
smatch version: v0.5.0-8994-gd50c5a4c

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/202601251908.baMDVVgW-lkp@intel.com/

smatch warnings:
drivers/crypto/xilinx/zynqmp-aes-gcm.c:556 xilinx_aes_aead_remove() warn: inconsistent indenting

vim +556 drivers/crypto/xilinx/zynqmp-aes-gcm.c

4d96f7d48131fe Kalyani Akula 2020-02-17  548  
56934489a80a74 Harsh Jain    2025-12-20  549  static void xilinx_aes_aead_remove(struct platform_device *pdev)
4d96f7d48131fe Kalyani Akula 2020-02-17  550  {
43f0478672c323 Harsh Jain    2025-12-20  551  	aead_dev = platform_get_drvdata(pdev);
43f0478672c323 Harsh Jain    2025-12-20  552  	crypto_engine_exit(aead_dev->engine);
43f0478672c323 Harsh Jain    2025-12-20  553  	for (int i = 0; aead_dev->aead_algs[i].dma_bit_mask; i++)
43f0478672c323 Harsh Jain    2025-12-20  554  		crypto_engine_unregister_aead(&aead_dev->aead_algs[i].aead);
4d96f7d48131fe Kalyani Akula 2020-02-17  555  
43f0478672c323 Harsh Jain    2025-12-20 @556  	 aead_dev = NULL;
75578e5c2040b5 Harsh Jain    2025-12-20  557  }
4d96f7d48131fe Kalyani Akula 2020-02-17  558  

:::::: The code at line 556 was first introduced by commit
:::::: 43f0478672c3239cd10fd460ae84ba2b3f55dc07 crypto: xilinx - Register H/W key support with paes

:::::: TO: Harsh Jain <h.jain@amd.com>
:::::: CC: Herbert Xu <herbert@gondor.apana.org.au>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-01-25 11:51 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=202601251908.baMDVVgW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=h.jain@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.