public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Next March 19: drivers/comedi build break.
Date: Thu, 19 Mar 2009 18:50:10 +0530	[thread overview]
Message-ID: <49C2468A.1040504@in.ibm.com> (raw)
In-Reply-To: <20090319221024.5e2ad6e5.sfr@canb.auug.org.au>

Next 19 randconfig build fails with :

  CC [M]  drivers/staging/comedi/comedi_fops.o
In file included from drivers/staging/comedi/comedidev.h:38,
                 from drivers/staging/comedi/comedi_fops.c:45:
drivers/staging/comedi/interrupt.h:25: error: conflicting types for ‘irqreturn_t’
include/linux/irqreturn.h:14: error: previous declaration of ‘irqreturn_t’ was here
In file included from drivers/staging/comedi/comedidev.h:38,
                 from drivers/staging/comedi/comedi_fops.c:45:
drivers/staging/comedi/interrupt.h:28:1: warning: "IRQ_RETVAL" redefined
In file included from include/linux/interrupt.h:10,
                 from drivers/staging/comedi/interrupt.h:22,
                 from drivers/staging/comedi/comedidev.h:38,
                 from drivers/staging/comedi/comedi_fops.c:45:
include/linux/irqreturn.h:15:1: warning: this is the location of the previous definition
make[3]: *** [drivers/staging/comedi/comedi_fops.o] Error 1

Probably because of the irqreturn_t related changes.

Thanks
-Sachin

-- 

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


  reply	other threads:[~2009-03-19 13:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 11:10 linux-next: Tree for March 19 Stephen Rothwell
2009-03-19 13:20 ` Sachin Sant [this message]
2009-03-19 15:33   ` Next March 19: drivers/comedi build break Greg KH
2009-03-19 18:51     ` Greg KH
2009-03-19 16:54 ` linux-next: Tree for March 19 (media/video/au0828) Randy Dunlap
2009-03-19 22:28   ` Mauro Carvalho Chehab
2009-03-19 17:07 ` linux-next: Tree for March 19 (staging/psb) Randy Dunlap
2009-03-19 18:51   ` Greg KH
2009-03-19 17:11 ` linux-next: Tree for March 19 (media/au8522) Randy Dunlap
2009-03-20  0:06   ` Mauro Carvalho Chehab
2009-03-19 17:13 ` linux-next: Tree for March 19 (media/video/cx231xx/) Randy Dunlap
2009-03-19 17:28 ` linux-next: Tree for March 19 (wireless/p54) Randy Dunlap
2009-03-19 17:50   ` Michael Buesch
2009-03-19 18:49     ` Randy Dunlap
2009-03-19 18:55       ` Michael Buesch
2009-03-20 23:57         ` [PATCH] p54: fix SoftLED compile dependencies Christian Lamparter
2009-03-21  6:36           ` Kalle Valo
2009-03-21 12:22             ` Christian Lamparter
2009-03-21 12:27               ` Kalle Valo
2009-03-21 15:26                 ` Larry Finger
2009-03-23 14:13               ` John W. Linville
2009-03-23 14:37                 ` [PATCH v2] " Christian Lamparter
2009-03-23  1:00           ` [PATCH] " Randy Dunlap
2009-03-23 14:14           ` John W. Linville

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=49C2468A.1040504@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox