linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>
Subject: Re: linux-next: Tree for March 19 (staging/psb)
Date: Thu, 19 Mar 2009 11:51:40 -0700	[thread overview]
Message-ID: <20090319185140.GB20608@kroah.com> (raw)
In-Reply-To: <49C27BBC.8070908@oracle.com>

On Thu, Mar 19, 2009 at 10:07:08AM -0700, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20090318:
> 
> 
> drivers/staging/psb/drm_os_linux.h:54: error: conflicting types for 'irqreturn_t'
> include/linux/irqreturn.h:14: error: previous declaration of 'irqreturn_t' was here

This one will be fixed tomorrow as I've pushed a new version of the
driver out that doesn't contain a new copy of the drm core.

> drivers/staging/psb/intel_reg.h:785:1: warning: "set_page_address" redefined
> include/linux/mm.h:622:1: warning: this is the location of the previous definition
> make[4]: *** [drivers/staging/psb/psb_drv.o] Error 1

Odd, I'll try to find this one.

thanks,

greg k-h

  reply	other threads:[~2009-03-19 18:53 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 ` Next March 19: drivers/comedi build break Sachin Sant
2009-03-19 15:33   ` 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 [this message]
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
     [not found]   ` <49C280BE.8090106-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-03-19 17:50     ` Michael Buesch
2009-03-19 18:49       ` Randy Dunlap
2009-03-19 18:55         ` Michael Buesch
     [not found]           ` <200903191955.00718.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
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
     [not found]                   ` <200903211322.01654.chunkeey-S0/GAf8tV78@public.gmane.org>
2009-03-21 12:27                     ` Kalle Valo
     [not found]                       ` <873ad7dpru.fsf-4yk3W8r0N7SEazanehQPrg@public.gmane.org>
2009-03-21 15:26                         ` Larry Finger
2009-03-23 14:13                     ` John W. Linville
     [not found]                       ` <20090323141320.GC3285-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
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=20090319185140.GB20608@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).