From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Doug Ledford <dledford@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: linux-next: Tree for Aug 17 (staging/hfi1)
Date: Wed, 19 Aug 2015 09:23:00 +1000 [thread overview]
Message-ID: <20150819092300.3e97d1ec@canb.auug.org.au> (raw)
In-Reply-To: <32E1700B9017364D9B60AED9960492BC257995D2@fmsmsx120.amr.corp.intel.com>
Hi Mike,
On Tue, 18 Aug 2015 14:24:32 +0000 "Marciniszyn, Mike" <mike.marciniszyn@intel.com> wrote:
>
> > 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, ...) \
> >
>
> This was corrected with
> https://www.mail-archive.com/linux-rdma@vger.kernel.org/msg27221.html, which I think Doug has picked up.
>
> Doug, Randy, Stephen how do we want to handle fixing drivers/staging/hfi1 via the staging list vs. the linux-rdma list?
Since the problem was only introduced in the rdma tree (and the trace.h
file only exists there), it needs to be fixed there.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
prev parent reply other threads:[~2015-08-18 23:23 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 ` linux-next: Tree for Aug 17 (staging/hfi1) Randy Dunlap
2015-08-18 14:24 ` Marciniszyn, Mike
2015-08-18 23:23 ` Stephen Rothwell [this message]
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=20150819092300.3e97d1ec@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=devel@driverdev.osuosl.org \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).