CC: [email protected]
CC: [email protected]
TO: Srujana Challa <[email protected]>
CC: Jakub Kicinski <[email protected]>
CC: Suheil Chandran <[email protected]>
CC: Lukasz Bartosik <[email protected]>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
master
head:   8baef6386baaefb776bdd09b5c7630cf057c51c6
commit: ae454086e3c227f78acb718249064aecb94da1e8 octeontx2-af: add mailbox 
interface for CPT
date:   8 months ago
:::::: branch date: 5 hours ago
:::::: commit date: 8 months ago
config: mips-randconfig-m031-20210723 (attached as .config)
compiler: mips64-linux-gcc (GCC) 10.3.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
Reported-by: Dan Carpenter <[email protected]>

smatch warnings:
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:1768 rvu_process_mbox_msg() 
warn: Function too hairy.  No more merges.

vim +1768 drivers/net/ethernet/marvell/octeontx2/af/rvu.c

9bdc47a6e3288b Tomasz Duszynski 2018-11-19  1764  
7304ac4567bcb7 Sunil Goutham    2018-10-10  1765  bad_message:
1f15462539829c Aleksey Makarov  2018-10-10  1766        default:
9bdc47a6e3288b Tomasz Duszynski 2018-11-19  1767                
otx2_reply_invalid_msg(mbox, devid, req->pcifunc, req->id);
7304ac4567bcb7 Sunil Goutham    2018-10-10 @1768                return -ENODEV;
7304ac4567bcb7 Sunil Goutham    2018-10-10  1769        }
1f15462539829c Aleksey Makarov  2018-10-10  1770  }
7304ac4567bcb7 Sunil Goutham    2018-10-10  1771  

:::::: The code at line 1768 was first introduced by commit
:::::: 7304ac4567bcb72fd57cc79582bf53ca7840136f octeontx2-af: Add mailbox IRQ 
and msg handlers

:::::: TO: Sunil Goutham <[email protected]>
:::::: CC: David S. Miller <[email protected]>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/[email protected]

Attachment: .config.gz
Description: application/gzip

_______________________________________________
kbuild mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to