From: kernel test robot <lkp@intel.com>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, vadim.fedorenko@linux.dev,
jiri@resnulli.us, corbet@lwn.net, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, linux-doc@vger.kernel.org,
intel-wired-lan@lists.osuosl.org,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: Re: [PATCH net-next 4/4] ice: dpll: implement phase related callbacks
Date: Wed, 27 Sep 2023 21:17:27 +0800 [thread overview]
Message-ID: <202309272113.rttl6e6s-lkp@intel.com> (raw)
In-Reply-To: <20230927092435.1565336-5-arkadiusz.kubalewski@intel.com>
Hi Arkadiusz,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Arkadiusz-Kubalewski/dpll-docs-add-support-for-pin-signal-phase-offset-adjust/20230927-172843
base: net-next/main
patch link: https://lore.kernel.org/r/20230927092435.1565336-5-arkadiusz.kubalewski%40intel.com
patch subject: [PATCH net-next 4/4] ice: dpll: implement phase related callbacks
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20230927/202309272113.rttl6e6s-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230927/202309272113.rttl6e6s-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/202309272113.rttl6e6s-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/intel/ice/ice_dpll.c:1064: warning: Function parameter or member 'phase_offset' not described in 'ice_dpll_phase_offset_get'
>> drivers/net/ethernet/intel/ice/ice_dpll.c:1064: warning: Excess function parameter 'phase_adjust' description in 'ice_dpll_phase_offset_get'
vim +1064 drivers/net/ethernet/intel/ice/ice_dpll.c
1039
1040 #define ICE_DPLL_PHASE_OFFSET_DIVIDER 100
1041 #define ICE_DPLL_PHASE_OFFSET_FACTOR \
1042 (DPLL_PHASE_OFFSET_DIVIDER / ICE_DPLL_PHASE_OFFSET_DIVIDER)
1043 /**
1044 * ice_dpll_phase_offset_get - callback for get dpll phase shift value
1045 * @pin: pointer to a pin
1046 * @pin_priv: private data pointer passed on pin registration
1047 * @dpll: registered dpll pointer
1048 * @dpll_priv: private data pointer passed on dpll registration
1049 * @phase_adjust: on success holds pin phase_adjust value
1050 * @extack: error reporting
1051 *
1052 * Dpll subsystem callback. Handler for getting phase shift value between
1053 * dpll's input and output.
1054 *
1055 * Context: Acquires pf->dplls.lock
1056 * Return:
1057 * * 0 - success
1058 * * negative - error
1059 */
1060 static int
1061 ice_dpll_phase_offset_get(const struct dpll_pin *pin, void *pin_priv,
1062 const struct dpll_device *dpll, void *dpll_priv,
1063 s64 *phase_offset, struct netlink_ext_ack *extack)
> 1064 {
1065 struct ice_dpll *d = dpll_priv;
1066 struct ice_pf *pf = d->pf;
1067
1068 mutex_lock(&pf->dplls.lock);
1069 if (d->active_input == pin)
1070 *phase_offset = d->phase_offset * ICE_DPLL_PHASE_OFFSET_FACTOR;
1071 else
1072 *phase_offset = 0;
1073 mutex_unlock(&pf->dplls.lock);
1074
1075 return 0;
1076 }
1077
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-27 13:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 9:24 [PATCH net-next 0/4] dpll: add phase-offset and phase-adjust Arkadiusz Kubalewski
2023-09-27 9:24 ` [PATCH net-next 1/4] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
2023-10-02 15:00 ` Jiri Pirko
2023-10-09 22:53 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [PATCH net-next 2/4] dpll: spec: add support for pin-dpll " Arkadiusz Kubalewski
2023-10-02 14:53 ` Jiri Pirko
2023-10-06 10:29 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [PATCH net-next 3/4] dpll: netlink/core: " Arkadiusz Kubalewski
2023-09-27 18:09 ` Vadim Fedorenko
2023-10-02 14:32 ` Kubalewski, Arkadiusz
2023-10-02 15:04 ` Jiri Pirko
2023-10-02 15:09 ` Vadim Fedorenko
2023-10-02 23:10 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-03 6:27 ` Jiri Pirko
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 17:18 ` Jiri Pirko
2023-10-04 9:13 ` Kubalewski, Arkadiusz
2023-10-02 23:03 ` Kubalewski, Arkadiusz
2023-10-03 6:32 ` Jiri Pirko
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 17:19 ` Jiri Pirko
2023-10-04 9:11 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [PATCH net-next 4/4] ice: dpll: implement phase related callbacks Arkadiusz Kubalewski
2023-09-27 13:17 ` kernel test robot [this message]
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=202309272113.rttl6e6s-lkp@intel.com \
--to=lkp@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).