public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Brian Foster <bfoster@redhat.com>
Cc: kbuild-all@01.org, linux-xfs@vger.kernel.org,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: [xfs-linux:xfs-4.15-merge 24/76] fs//xfs/xfs_buf.c:2136: warning: unused variable 'mp'
Date: Fri, 27 Oct 2017 15:27:30 +0800	[thread overview]
Message-ID: <201710271527.DFIgRssJ%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git xfs-4.15-merge
head:   9c92ee208b1faa0ef2cc899b85fd0607b6fac7fe
commit: 7561d27e90fa0df0aac2a1d6b49c2a28eaae7026 [24/76] xfs: buffer lru reference count error injection tag
config: x86_64-randconfig-a0-10271430 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
        git checkout 7561d27e90fa0df0aac2a1d6b49c2a28eaae7026
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   fs//xfs/xfs_buf.c: In function 'xfs_buf_set_ref':
>> fs//xfs/xfs_buf.c:2136: warning: unused variable 'mp'

vim +/mp +2136 fs//xfs/xfs_buf.c

  2133	
  2134	void xfs_buf_set_ref(struct xfs_buf *bp, int lru_ref)
  2135	{
> 2136		struct xfs_mount	*mp = bp->b_target->bt_mount;

---
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: 35665 bytes --]

             reply	other threads:[~2017-10-27  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  7:27 kbuild test robot [this message]
2017-10-27 10:22 ` [PATCH] xfs: fix unused variable warning in xfs_buf_set_ref() Brian Foster
2017-10-27 16:21   ` Darrick J. Wong

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=201710271527.DFIgRssJ%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=kbuild-all@01.org \
    --cc=linux-xfs@vger.kernel.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