linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 51/95] drivers/gpu/drm/ttm/ttm_page_alloc.c:451:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result
Date: Wed, 22 Nov 2017 11:39:02 +0800	[thread overview]
Message-ID: <201711221159.FF6CRNDf%fengguang.wu@intel.com> (raw)

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

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   f5ef1cb6700e8b570adae945b1e0bd4ab95d8a26
commit: a58c5788f373a7a45532d5b02ae3b0173d4273e7 [51/95] mm,vmscan: mark register_shrinker() as __must_check
config: i386-randconfig-i1-201747 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
        git checkout a58c5788f373a7a45532d5b02ae3b0173d4273e7
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/ttm/ttm_page_alloc.c: In function 'ttm_pool_mm_shrink_init':
>> drivers/gpu/drm/ttm/ttm_page_alloc.c:451:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result [-Wunused-result]
     register_shrinker(&manager->mm_shrink);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
   drivers/gpu/drm/ttm/ttm_page_alloc_dma.c: In function 'ttm_dma_pool_mm_shrink_init':
>> drivers/gpu/drm/ttm/ttm_page_alloc_dma.c:1185:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result [-Wunused-result]
     register_shrinker(&manager->mm_shrink);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

vim +/register_shrinker +451 drivers/gpu/drm/ttm/ttm_page_alloc.c

1403b1a3 Pauli Nieminen 2010-04-01  445  
1403b1a3 Pauli Nieminen 2010-04-01  446  static void ttm_pool_mm_shrink_init(struct ttm_pool_manager *manager)
1403b1a3 Pauli Nieminen 2010-04-01  447  {
7dc19d5a Dave Chinner   2013-08-28  448  	manager->mm_shrink.count_objects = ttm_pool_shrink_count;
7dc19d5a Dave Chinner   2013-08-28  449  	manager->mm_shrink.scan_objects = ttm_pool_shrink_scan;
1403b1a3 Pauli Nieminen 2010-04-01  450  	manager->mm_shrink.seeks = 1;
1403b1a3 Pauli Nieminen 2010-04-01 @451  	register_shrinker(&manager->mm_shrink);
1403b1a3 Pauli Nieminen 2010-04-01  452  }
1403b1a3 Pauli Nieminen 2010-04-01  453  

:::::: The code at line 451 was first introduced by commit
:::::: 1403b1a38e8b19a4cc17e2c158e278628943a436 drm/ttm: add pool wc/uc page allocator V3

:::::: TO: Pauli Nieminen <suokkos@gmail.com>
:::::: CC: Dave Airlie <airlied@redhat.com>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

                 reply	other threads:[~2017-11-22  3:39 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=201711221159.FF6CRNDf%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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