From: kernel test robot <lkp@intel.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [ragnatech:next/net/tsn 4/5] drivers/net/ethernet/renesas/rtsn.c:270:9: error: implicit declaration of function '__iowmb'
Date: Mon, 27 Nov 2023 11:33:15 +0800 [thread overview]
Message-ID: <202311271132.APTExKBp-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/niklas/linux.git next/net/tsn
head: 9929703c4bd6c8c37ff9c65353ea241101007b52
commit: 2aec3957074d82d65a9df406a07631e6a81e7a98 [4/5] net: ethernet: rtsn: Add support for Renesas Ethernet-TSN
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20231127/202311271132.APTExKBp-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231127/202311271132.APTExKBp-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/202311271132.APTExKBp-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/ethernet/renesas/rtsn.c: In function 'rtsn_poll':
>> drivers/net/ethernet/renesas/rtsn.c:270:9: error: implicit declaration of function '__iowmb' [-Werror=implicit-function-declaration]
270 | __iowmb();
| ^~~~~~~
cc1: some warnings being treated as errors
vim +/__iowmb +270 drivers/net/ethernet/renesas/rtsn.c
244
245 static int rtsn_poll(struct napi_struct *napi, int budget)
246 {
247 struct rtsn_private *priv;
248 struct net_device *ndev;
249 unsigned long flags;
250 int quota = budget;
251
252 ndev = napi->dev;
253 priv = netdev_priv(ndev);
254
255 /* Processing RX Descriptor Ring */
256 if (rtsn_rx(ndev, "a))
257 goto out;
258
259 /* Processing TX Descriptor Ring */
260 spin_lock_irqsave(&priv->lock, flags);
261 rtsn_tx_free(ndev, true);
262 netif_wake_subqueue(ndev, 0);
263 spin_unlock_irqrestore(&priv->lock, flags);
264
265 napi_complete(napi);
266
267 /* Re-enable TX/RX interrupts */
268 spin_lock_irqsave(&priv->lock, flags);
269 rtsn_ctrl_data_irq(priv, true);
> 270 __iowmb();
271 spin_unlock_irqrestore(&priv->lock, flags);
272 out:
273 return budget - quota;
274 }
275
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-27 3:33 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=202311271132.APTExKBp-lkp@intel.com \
--to=lkp@intel.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--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.