From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Mike Marciniszyn <mike.marciniszyn@intel.com>
Subject: Re: linux-next: Tree for Aug 17 (staging/hfi1)
Date: Mon, 17 Aug 2015 15:35:54 -0700 [thread overview]
Message-ID: <55D261CA.2070802@infradead.org> (raw)
In-Reply-To: <20150817205533.72ebb3fb@canb.auug.org.au>
On 08/17/15 03:55, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150813:
>
Several items:
A: these and other similar errors:
In file included from ../drivers/staging/hfi1/chip.c:61:0:
../drivers/staging/hfi1/chip.c: In function â__hfi1_trace_LINKVERBâ:
../drivers/staging/hfi1/trace.h:1357:20: error: function â__hfi1_trace_LINKVERBâ can never be inlined because it uses variable argument lists
static inline void __hfi1_trace_##fn(const char *func, char *fmt, ...) \
^
../drivers/staging/hfi1/chip.c: In function â__hfi1_trace_CNTRâ:
../drivers/staging/hfi1/trace.h:1357:20: error: function â__hfi1_trace_CNTRâ can never be inlined because it uses variable argument lists
static inline void __hfi1_trace_##fn(const char *func, char *fmt, ...) \
^
../drivers/staging/hfi1/chip.c: In function â__hfi1_trace_DC8051â:
../drivers/staging/hfi1/trace.h:1357:20: error: function â__hfi1_trace_DC8051â can never be inlined because it uses variable argument lists
static inline void __hfi1_trace_##fn(const char *func, char *fmt, ...) \
^
../drivers/staging/hfi1/chip.c: In function â__hfi1_trace_RCVCTRLâ:
../drivers/staging/hfi1/trace.h:1357:20: error: function â__hfi1_trace_RCVCTRLâ can never be inlined because it uses variable argument lists
static inline void __hfi1_trace_##fn(const char *func, char *fmt, ...) \
^
../drivers/staging/hfi1/chip.c: In function â__hfi1_trace_TIDâ:
../drivers/staging/hfi1/trace.h:1357:20: error: function â__hfi1_trace_TIDâ can never be inlined because it uses variable argument lists
static inline void __hfi1_trace_##fn(const char *func, char *fmt, ...) \
^
B: When CONFIG_PCI is not enabled, lots of these errors:
In file included from ../drivers/staging/hfi1/chip.c:60:0:
../drivers/staging/hfi1/hfi.h:508:20: error: field âmsixâ has incomplete type
struct msix_entry msix;
^
../drivers/staging/hfi1/chip.c: In function âdisable_intxâ:
../drivers/staging/hfi1/chip.c:8667:2: error: implicit declaration of function âpci_intxâ [-Werror=implicit-function-declaration]
pci_intx(pdev, 0);
^
so the driver should depend on PCI or maybe even PCI_MSI.
C. Please provide some contact info, e.g. in a TODO file or the MAINTAINERS file.
--
~Randy
next prev parent reply other threads:[~2015-08-17 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 10:55 linux-next: Tree for Aug 17 Stephen Rothwell
2015-08-17 17:34 ` linux-next: Tree for Aug 17 (mshyperv.c) Randy Dunlap
2015-08-17 17:53 ` KY Srinivasan
2015-08-17 22:35 ` Randy Dunlap [this message]
2015-08-18 14:24 ` linux-next: Tree for Aug 17 (staging/hfi1) Marciniszyn, Mike
2015-08-18 23:23 ` Stephen Rothwell
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=55D261CA.2070802@infradead.org \
--to=rdunlap@infradead.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).