From: kernel test robot <lkp@intel.com>
To: Vishvambar Panth S <vishvambarpanth.s@microchip.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, kuba@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, bryan.whitehead@microchip.com,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, richardcochran@gmail.com
Subject: Re: [PATCH v2 net-next] net: microchip: lan743x: improve throughput with rx timestamp config
Date: Tue, 17 Oct 2023 23:55:37 +0800 [thread overview]
Message-ID: <202310172343.lfyTHDCw-lkp@intel.com> (raw)
In-Reply-To: <20231017180542.30613-1-vishvambarpanth.s@microchip.com>
Hi Vishvambar,
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/Vishvambar-Panth-S/net-microchip-lan743x-improve-throughput-with-rx-timestamp-config/20231017-180453
base: net-next/main
patch link: https://lore.kernel.org/r/20231017180542.30613-1-vishvambarpanth.s%40microchip.com
patch subject: [PATCH v2 net-next] net: microchip: lan743x: improve throughput with rx timestamp config
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20231017/202310172343.lfyTHDCw-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/20231017/202310172343.lfyTHDCw-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/202310172343.lfyTHDCw-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/microchip/lan743x_main.c:1873:6: warning: no previous prototype for 'lan743x_rx_cfg_b_tstamp_config' [-Wmissing-prototypes]
1873 | void lan743x_rx_cfg_b_tstamp_config(struct lan743x_adapter *adapter,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/lan743x_rx_cfg_b_tstamp_config +1873 drivers/net/ethernet/microchip/lan743x_main.c
1872
> 1873 void lan743x_rx_cfg_b_tstamp_config(struct lan743x_adapter *adapter,
1874 int rx_ts_config)
1875 {
1876 int channel_number;
1877 int index;
1878 u32 data;
1879
1880 for (index = 0; index < LAN743X_USED_RX_CHANNELS; index++) {
1881 channel_number = adapter->rx[index].channel_number;
1882 data = lan743x_csr_read(adapter, RX_CFG_B(channel_number));
1883 data &= RX_CFG_B_TS_MASK_;
1884 data |= rx_ts_config;
1885 lan743x_csr_write(adapter, RX_CFG_B(channel_number),
1886 data);
1887 }
1888 }
1889
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-10-17 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 18:05 [PATCH v2 net-next] net: microchip: lan743x: improve throughput with rx timestamp config Vishvambar Panth S
2023-10-17 15:55 ` 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=202310172343.lfyTHDCw-lkp@intel.com \
--to=lkp@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vishvambarpanth.s@microchip.com \
/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).