From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [nfc:nfc-next 19/20] net/nfc/hci/llc_shdlc.c:830:28: sparse: non-ANSI function declaration of functi
Date: Fri, 14 Sep 2012 02:20:24 +0000 [thread overview]
Message-ID: <20120914022024.GA10467@localhost> (raw)
Hi Eric,
FYI, there are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-3.0.git nfc-next
head: 73fecc5ce0bba7aa0cc8719529964b55e00c00bc
commit: f36d3d026c8c53522e4875ce74054c9b9f87b99b [19/20] NFC: Add an shdlc llc module to llc core
All sparse warnings:
+ net/nfc/hci/llc_shdlc.c:830:28: sparse: non-ANSI function declaration of function 'nfc_llc_shdlc_register'
vim +830 net/nfc/hci/llc_shdlc.c
820
821 static struct nfc_llc_ops llc_shdlc_ops = {
822 .init = llc_shdlc_init,
823 .deinit = llc_shdlc_deinit,
824 .start = llc_shdlc_start,
825 .stop = llc_shdlc_stop,
826 .rcv_from_drv = llc_shdlc_rcv_from_drv,
827 .xmit_from_hci = llc_shdlc_xmit_from_hci,
828 };
829
> 830 int nfc_llc_shdlc_register()
831 {
832 return nfc_llc_register(LLC_SHDLC_NAME, &llc_shdlc_ops);
833 }
834 EXPORT_SYMBOL(nfc_llc_shdlc_register);
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-09-14 2:20 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=20120914022024.GA10467@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.