linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-pcmcia@lists.infradead.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 2 (scsi/pcmcia)
Date: Mon, 2 Aug 2010 22:10:38 +0200	[thread overview]
Message-ID: <20100802201038.GB21063@comet.dominikbrodowski.net> (raw)
In-Reply-To: <20100802102707.5fbd9072.randy.dunlap@oracle.com>

Hey,

On Mon, Aug 02, 2010 at 10:27:07AM -0700, Randy Dunlap wrote:
> pcmcia changes cause these build errors in drivers/scsi/pcmcia/nsp_cs.c:
> 
> drivers/scsi/pcmcia/nsp_cs.c:1907:1: error: unterminated argument list invoking macro "release_region"
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: 'release_region' undeclared (first use in this function)
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: (Each undeclared identifier is reported only once
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: for each function it appears in.)
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: expected ';' at end of input
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: expected declaration or statement at end of input
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: expected declaration or statement at end of input
> drivers/scsi/pcmcia/nsp_cs.c:1720: error: expected declaration or statement at end of input

ah, this driver depends on !x86_64, so my make allmodconfig run didn't catch
it... Thanks!

Should be fixed for the next -next.

Best,
	Dominik

  reply	other threads:[~2010-08-02 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  4:44 linux-next: Tree for August 2 Stephen Rothwell
2010-08-02 17:27 ` linux-next: Tree for August 2 (scsi/pcmcia) Randy Dunlap
2010-08-02 20:10   ` Dominik Brodowski [this message]
2010-08-02 17:52 ` [PATCH -next] apparmor: depends on NET Randy Dunlap
2010-08-03  2:43   ` John Johansen
2010-08-05  3:15     ` James Morris

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=20100802201038.GB21063@comet.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=randy.dunlap@oracle.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).