public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Mike Marciniszyn <infinipath@intel•com>,
	linux-rdma@vger•kernel.org
Subject: Re: linux-next: Tree for Jun 21 (infiniband: qib)
Date: Fri, 21 Jun 2013 08:30:05 -0700	[thread overview]
Message-ID: <51C4717D.4090002@infradead.org> (raw)
In-Reply-To: <20130621181721.11783d80583444868725b62c@canb.auug.org.au>

On 06/21/13 01:17, Stephen Rothwell wrote:
> Hi all,
> 
> Happy solstice!
> 
> Changes since 20130620:
> 


on x86_64:

when CONFIG_SMP is not enabled:

(from qib.h:)

#ifdef CONFIG_INFINIBAND_QIB_DCA
struct qib_irq_notify {
	int rcv;
	void *arg;
	struct irq_affinity_notify notify;
};
#endif

struct irq_affinity_notify is only defined for CONFIG_SMP or GENERIC_HARDIRQS.
Build error happens when one of those is not enabled.


In file included from drivers/infiniband/hw/qib/qib_cq.c:41:0:
drivers/infiniband/hw/qib/qib.h:447:29: error: field 'notify' has incomplete type
make[4]: *** [drivers/infiniband/hw/qib/qib_cq.o] Error 1




-- 
~Randy

  parent reply	other threads:[~2013-06-21 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  8:17 linux-next: Tree for Jun 21 Stephen Rothwell
2013-06-21 15:22 ` linux-next: Tree for Jun 21 (netdev: openvswitch) Randy Dunlap
2013-06-21 23:18   ` Jesse Gross
2013-06-21 15:30 ` Randy Dunlap [this message]
     [not found]   ` <51C4717D.4090002-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-06-21 15:31     ` linux-next: Tree for Jun 21 (infiniband: qib) Marciniszyn, Mike

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=51C4717D.4090002@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=infinipath@intel$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-rdma@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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