From: Stephen Hemminger <stephen@networkplumber.org>
To: Ilya Dryomov <idryomov@gmail.com>, "Yan, Zheng" <zyan@redhat.com>,
Sage Weil <sage@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Kernel warnings in CEPH
Date: Thu, 18 May 2017 17:06:13 -0700 [thread overview]
Message-ID: <20170518170613.5e1d924f@xeon-e3> (raw)
Building kernel with CEPH and warnings enabled shows several missing
prototypes and unused variables. Please fix.
net/ceph/ceph_common.c:62:13: warning: no previous prototype for ‘ceph_file_part’ [-Wmissing-prototypes]
net/ceph/messenger.c: In function ‘write_partial_message_data’:
net/ceph/messenger.c:1580:8: warning: variable ‘need_crc’ set but not used [-Wunused-but-set-variable]
net/ceph/mon_client.c: In function ‘ceph_monmap_decode’:
net/ceph/mon_client.c:46:6: warning: variable ‘version’ set but not used [-Wunused-but-set-variable]
net/ceph/auth_x.c: In function ‘process_one_ticket’:
net/ceph/auth_x.c:146:19: warning: variable ‘blob_struct_v’ set but not used [-Wunused-but-set-variable]
next reply other threads:[~2017-05-19 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 0:06 Stephen Hemminger [this message]
2017-05-19 2:49 ` Kernel warnings in CEPH Jos Collin
2017-05-19 6:57 ` Ilya Dryomov
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=20170518170613.5e1d924f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=sage@redhat.com \
--cc=zyan@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.