All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Next April 6 : x86 allmodconfig failure [drivers/pci]
Date: Mon, 06 Apr 2009 15:14:51 +0530	[thread overview]
Message-ID: <49D9CF13.60202@in.ibm.com> (raw)
In-Reply-To: <20090406164555.e1232116.sfr@canb.auug.org.au>

Today's next tree allmodconfig build on x86 failed with

drivers/pci/intel-iommu.c:2636:35: error: macro "if" passed 2 arguments, but takes just 1
drivers/pci/intel-iommu.c: In function init_iommu_hw:
drivers/pci/intel-iommu.c:2636: error: expected ( before { token
drivers/pci/intel-iommu.c:2637: error: ______r undeclared (first use in this function)
drivers/pci/intel-iommu.c:2637: error: (Each undeclared identifier is reported only once
drivers/pci/intel-iommu.c:2637: error: for each function it appears in.)
drivers/pci/intel-iommu.c:2640:35: error: macro "if" passed 2 arguments, but takes just 1
drivers/pci/intel-iommu.c:2640: error: expected ( before { token

and many more of such errors. Similar errors with intr_remapping.c

drivers/pci/intr_remapping.c:679:28: error: macro "if" passed 2 arguments, but takes just 1
drivers/pci/intr_remapping.c: In function disable_intr_remapping:
drivers/pci/intr_remapping.c:679: error: expected ( before { token
drivers/pci/intr_remapping.c:693:28: error: macro "if" passed 2 arguments, but takes just 1
......

Thanks
-Sachin



-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

  reply	other threads:[~2009-04-06  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  6:45 linux-next: Tree for April 6 Stephen Rothwell
2009-04-06  9:44 ` Sachin Sant [this message]
2009-04-06 16:06   ` Next April 6 : x86 allmodconfig failure [drivers/pci] Alexander Beregalov
2009-04-07  5:27   ` Jike Song

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=49D9CF13.60202@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.