From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [ceph:wip-tunables 10/10] net/ceph/crush/mapper.c:309:21: warning: unused variable 'orig_tries'
Date: Thu, 12 Jul 2012 23:42:42 +0000 [thread overview]
Message-ID: <20120712234242.GA5608@localhost> (raw)
Hi caleb,
There are new compile warnings show up in
tree: git://github.com/ceph/ceph-client.git wip-tunables
head: 891d71b246d89f03fce85c6503d2429fbe628114
commit: 891d71b246d89f03fce85c6503d2429fbe628114 [10/10] CRUSH: allow OSD's to decode crush tunables
All warnings:
net/ceph/crush/mapper.c: In function 'crush_choose':
net/ceph/crush/mapper.c:309:21: warning: unused variable 'orig_tries' [-Wunused-variable]
net/ceph/osdmap.c: In function 'crush_decode':
net/ceph/osdmap.c:302:2: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
vim +309 net/ceph/crush/mapper.c
306 int item = 0;
307 int itemtype;
308 int collide, reject;
> 309 const unsigned int orig_tries = 5; /* attempts before we fall back to search */
310
311 dprintk("CHOOSE%s bucket %d x %d outpos %d numrep %d\n", recurse_to_leaf ? "_LEAF" : "",
312 bucket->id, x, outpos, numrep);
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-07-12 23:42 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=20120712234242.GA5608@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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