From: kernel test robot <lkp@intel.com>
To: Michal Kubiak <michal.kubiak@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: [alobakin:idpf-libie 32/36] drivers/net/ethernet/intel/idpf/idpf_txrx.c:747: warning: Function parameter or member 'arg' not described in 'idpf_xdp_rxq_info_init'
Date: Wed, 20 Dec 2023 01:06:16 +0800 [thread overview]
Message-ID: <202312200100.eqIFXLJr-lkp@intel.com> (raw)
tree: https://github.com/alobakin/linux idpf-libie
head: 53bb970b70f1017bf36da5a9067d2e04617b4f49
commit: ded9bfd3402769c0e3ef15041f46b55ce22c590d [32/36] idpf: prepare structures to support xdp
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20231220/202312200100.eqIFXLJr-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231220/202312200100.eqIFXLJr-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/202312200100.eqIFXLJr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/intel/idpf/idpf_txrx.c:747: warning: Function parameter or member 'arg' not described in 'idpf_xdp_rxq_info_init'
>> drivers/net/ethernet/intel/idpf/idpf_txrx.c:747: warning: Excess function parameter 'splitq' description in 'idpf_xdp_rxq_info_init'
>> drivers/net/ethernet/intel/idpf/idpf_txrx.c:777: warning: Function parameter or member 'arg' not described in 'idpf_xdp_rxq_info_deinit'
vim +747 drivers/net/ethernet/intel/idpf/idpf_txrx.c
738
739 /**
740 * idpf_xdp_rxq_info_init - Setup XDP RxQ info for a given Rx queue
741 * @rxq: Rx queue for which the resources are setup
742 * @splitq: flag indicating if the HW works in split queue mode
743 *
744 * Return: 0 on success, negative on failure.
745 */
746 static int idpf_xdp_rxq_info_init(struct idpf_queue *rxq, void *arg)
> 747 {
748 const struct idpf_vport *vport = rxq->vport;
749 const struct page_pool *pp;
750 struct xdp_mem_info *mem;
751 int err;
752
753 err = __xdp_rxq_info_reg(&rxq->xdp_rxq, vport->netdev, rxq->idx,
754 rxq->q_vector->napi.napi_id,
755 rxq->rx_buf_size);
756 if (err)
757 return err;
758
759 pp = arg ? rxq->rxq_grp->splitq.bufq_sets[0].bufq.pp : rxq->pp;
760
761 /* Memory model is already registered by libie, just copy the ID */
762 mem = &rxq->xdp_rxq.mem;
763 mem->type = MEM_TYPE_PAGE_POOL;
764 mem->id = pp->xdp_mem_id;
765
766 rxq->xdpqs = vport->txqs[vport->xdp_txq_offset];
767 rxq->num_xdp_txq = vport->num_xdp_txq;
768
769 return 0;
770 }
771
772 /**
773 * idpf_xdp_rxq_info_deinit - Deinit XDP RxQ info for a given Rx queue
774 * @rxq: Rx queue for which the resources are destroyed
775 */
776 static int idpf_xdp_rxq_info_deinit(struct idpf_queue *rxq, void *arg)
> 777 {
778 rxq->xdpqs = NULL;
779 rxq->num_xdp_txq = 0;
780
781 /* Memory model is managed by libie */
782 memset(&rxq->xdp_rxq, 0, sizeof(rxq->xdp_rxq));
783
784 return 0;
785 }
786
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-19 17:07 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=202312200100.eqIFXLJr-lkp@intel.com \
--to=lkp@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=llvm@lists.linux.dev \
--cc=michal.kubiak@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.