From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [sfc:for-davem 18/22] sparse: undefined identifier 'MCDI_EVENT_CODE_PTP_PPS'
Date: Thu, 19 Jul 2012 00:06:22 +0000 [thread overview]
Message-ID: <20120719000622.GA5548@localhost> (raw)
Hi Stuart,
There are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next for-davem
head: 2482aab313c3657557f1dad4c1b20c0934b84919
commit: 3d230d2a2c441aec6ba495341623c8086e926bec [18/22] sfc: Allow efx_mcdi_rpc to be called in two parts
All sparse warnings:
+ drivers/net/ethernet/sfc/mcdi.c:583:14: sparse: undefined identifier 'MCDI_EVENT_CODE_PTP_PPS'
+ drivers/net/ethernet/sfc/mcdi.c:584:17: sparse: undefined identifier 'efx_ptp_event'
+ drivers/net/ethernet/sfc/mcdi.c:583:14: sparse: incompatible types for 'case' statement
+ drivers/net/ethernet/sfc/mcdi.c:583:14: sparse: Expected constant expression in case statement
drivers/net/ethernet/sfc/mcdi.c: In function 'efx_mcdi_process_event':
drivers/net/ethernet/sfc/mcdi.c:583:7: error: 'MCDI_EVENT_CODE_PTP_PPS' undeclared (first use in this function)
drivers/net/ethernet/sfc/mcdi.c:583:7: note: each undeclared identifier is reported only once for each function it appears in
drivers/net/ethernet/sfc/mcdi.c:584:3: error: implicit declaration of function 'efx_ptp_event' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
vim +583 drivers/net/ethernet/sfc/mcdi.c
580 break;
581 case MCDI_EVENT_CODE_PTP_RX:
582 case MCDI_EVENT_CODE_PTP_FAULT:
> 583 case MCDI_EVENT_CODE_PTP_PPS:
584 efx_ptp_event(efx, event);
585 break;
586
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-07-19 0:06 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=20120719000622.GA5548@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 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.