All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:pr/639 4388/24603] drivers/crypto/caam/jr.c:344: warning: Function parameter or member 'idx' not described in 'caam_jridx_alloc'
Date: Fri, 1 Sep 2023 14:31:40 +0800	[thread overview]
Message-ID: <202309011415.vmjjiVOn-lkp@intel.com> (raw)

tree:   https://github.com/Freescale/linux-fslc pr/639
head:   857fbf7cebaba3b1ffccc558deee1d13ac0e11d7
commit: cf6c9073ad386aba7f02cce1ca1d49137b43dbc5 [4388/24603] crypto: caam - add functionality used by the caam_dma driver
config: arm-defconfig (https://download.01.org/0day-ci/archive/20230901/202309011415.vmjjiVOn-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230901/202309011415.vmjjiVOn-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/202309011415.vmjjiVOn-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/crypto/caam/jr.c:344: warning: Function parameter or member 'idx' not described in 'caam_jridx_alloc'


vim +344 drivers/crypto/caam/jr.c

   336	
   337	/**
   338	 * caam_jridx_alloc() - Alloc a specific job ring based on its index.
   339	 *
   340	 * returns :  pointer to the newly allocated physical
   341	 *	      JobR dev can be written to if successful.
   342	 **/
   343	struct device *caam_jridx_alloc(int idx)
 > 344	{
   345		struct caam_drv_private_jr *jrpriv;
   346		struct device *dev = ERR_PTR(-ENODEV);
   347	
   348		spin_lock(&driver_data.jr_alloc_lock);
   349	
   350		if (list_empty(&driver_data.jr_list))
   351			goto end;
   352	
   353		list_for_each_entry(jrpriv, &driver_data.jr_list, list_node) {
   354			if (jrpriv->ridx == idx) {
   355				atomic_inc(&jrpriv->tfm_count);
   356				dev = jrpriv->dev;
   357				break;
   358			}
   359		}
   360	
   361	end:
   362		spin_unlock(&driver_data.jr_alloc_lock);
   363		return dev;
   364	}
   365	EXPORT_SYMBOL(caam_jridx_alloc);
   366	

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

                 reply	other threads:[~2023-09-01  6:32 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=202309011415.vmjjiVOn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=otavio@ossystems.com.br \
    /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.