[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201904110915.9jPFP0Co%lkp@intel.com>
Date:   Thu, 11 Apr 2019 09:58:50 +0800
From:   kbuild test robot <lkp@...el.com>
To:     Mike Marshall <hubcap@...ibond.com>
Cc:     kbuild-all@...org, Martin Brandenburg <martin@...ibond.com>,
        devel@...ts.orangefs.org, linux-kernel@...r.kernel.org
Subject: [hubcap:for-next 20/22] fs/orangefs/file.c:574:5: sparse: symbol
 'orangefs_file_open' was not declared. Should it be static?
tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux for-next
head:   6055a739910e69f8f76120d48e7ae74a13b1fdda
commit: 9a959aaffd7090810eade53e4d960614405f57c6 [20/22] orangefs: remember count when reading.
reproduce:
        # apt-get install sparse
        git checkout 9a959aaffd7090810eade53e4d960614405f57c6
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
>> fs/orangefs/file.c:574:5: sparse: symbol 'orangefs_file_open' was not declared. Should it be static?
   fs/orangefs/file.c:580:5: sparse: symbol 'orangefs_flush' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
Powered by blists - more mailing lists
 
