All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [alobakin:idpf-libie 9/18] drivers/net/ethernet/intel/libie/rx.c:18: warning: Function parameter or member 'pp' not described in 'libie_rx_hw_len'
Date: Thu, 30 Nov 2023 05:36:10 +0800	[thread overview]
Message-ID: <202311300213.f55howeK-lkp@intel.com> (raw)

tree:   https://github.com/alobakin/linux idpf-libie
head:   06e16df156eea0862b47e50485e17c70c3d8ea8f
commit: 58f0ab910da24eae9c4021b2ebac59d8cc8cc905 [9/18] libie: add Rx buffer management (via Page Pool)
config: microblaze-allmodconfig (https://download.01.org/0day-ci/archive/20231130/202311300213.f55howeK-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231130/202311300213.f55howeK-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/202311300213.f55howeK-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/net/ethernet/intel/libie/rx.c:18: warning: Function parameter or member 'pp' not described in 'libie_rx_hw_len'
>> drivers/net/ethernet/intel/libie/rx.c:18: warning: Excess function parameter 'dev' description in 'libie_rx_hw_len'
>> drivers/net/ethernet/intel/libie/rx.c:18: warning: Excess function parameter 'max_len' description in 'libie_rx_hw_len'


vim +18 drivers/net/ethernet/intel/libie/rx.c

     7	
     8	/**
     9	 * libie_rx_hw_len - get the actual buffer size to be passed to HW
    10	 * @dev: &net_device to calculate the size for
    11	 * @max_len: maximum length for the given page size
    12	 *
    13	 * Return: HW-writeable length per one buffer to pass it to the HW accounting:
    14	 * MTU the @dev has, HW required alignment, minimum and maximum allowed values,
    15	 * and system's page size.
    16	 */
    17	static u32 libie_rx_hw_len(const struct page_pool_params *pp)
  > 18	{
    19		u32 len;
    20	
    21		len = READ_ONCE(pp->netdev->mtu) + LIBIE_RX_LL_LEN;
    22		len = ALIGN(len, LIBIE_RX_BUF_LEN_ALIGN);
    23		len = clamp(len, LIBIE_MIN_RX_BUF_LEN, pp->max_len);
    24	
    25		return len;
    26	}
    27	

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

                 reply	other threads:[~2023-11-29 21:36 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=202311300213.f55howeK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --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.