public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: dingsenjie@163.com, sfrench@samba.org, samba-technical@lists.samba.org
Cc: kbuild-all@lists.01.org, linux-cifs@vger.kernel.org,
	linux-kernel@vger.kernel.org, dingsenjie <dingsenjie@yulong.com>
Subject: Re: [PATCH] fs/cifs:simplify the return expression of cifs_swn_auth_info_krb
Date: Wed, 24 Feb 2021 15:02:55 +0800	[thread overview]
Message-ID: <202102241432.do2NllVq-lkp@intel.com> (raw)
In-Reply-To: <20210224033202.44052-1-dingsenjie@163.com>

[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]

Hi,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on cifs/for-next]
[also build test ERROR on v5.11 next-20210223]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/dingsenjie-163-com/fs-cifs-simplify-the-return-expression-of-cifs_swn_auth_info_krb/20210224-122502
base:   git://git.samba.org/sfrench/cifs-2.6.git for-next
config: s390-randconfig-r022-20210223 (attached as .config)
compiler: s390-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/2b5765f734346617361817a3b6cefea209078b3f
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review dingsenjie-163-com/fs-cifs-simplify-the-return-expression-of-cifs_swn_auth_info_krb/20210224-122502
        git checkout 2b5765f734346617361817a3b6cefea209078b3f
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs/cifs/cifs_swn.c: In function 'cifs_swn_auth_info_krb':
>> fs/cifs/cifs_swn.c:37:9: error: expected expression before '=' token
      37 |  return = nla_put_flag(skb, CIFS_GENL_ATTR_SWN_KRB_AUTH);
         |         ^
   fs/cifs/cifs_swn.c:38:1: error: control reaches end of non-void function [-Werror=return-type]
      38 | }
         | ^
   cc1: some warnings being treated as errors


vim +37 fs/cifs/cifs_swn.c

    34	
    35	static int cifs_swn_auth_info_krb(struct cifs_tcon *tcon, struct sk_buff *skb)
    36	{
  > 37		return = nla_put_flag(skb, CIFS_GENL_ATTR_SWN_KRB_AUTH);
    38	}
    39	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32186 bytes --]

      reply	other threads:[~2021-02-24  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  3:32 [PATCH] fs/cifs:simplify the return expression of cifs_swn_auth_info_krb dingsenjie
2021-02-24  7:02 ` 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=202102241432.do2NllVq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dingsenjie@163.com \
    --cc=dingsenjie@yulong.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    /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