From: Greg KH <greg@kroah.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-next@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: linux-next: v4l-dvb tree build failure
Date: Fri, 7 Nov 2008 10:41:48 -0800 [thread overview]
Message-ID: <20081107184148.GA2320@kroah.com> (raw)
In-Reply-To: <1226079837.11596.19.camel@brick>
On Fri, Nov 07, 2008 at 09:43:57AM -0800, Harvey Harrison wrote:
> On Fri, 2008-11-07 at 14:30 +1100, Stephen Rothwell wrote:
> > Hi Mauro,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > drivers/staging/go7007/go7007-v4l2.c: In function 'go7007_ioctl':
> > drivers/staging/go7007/go7007-v4l2.c:1338: warning: passing argument 1 of 'video_usercopy' from incompatible pointer type
> > drivers/staging/go7007/go7007-v4l2.c:1338: warning: passing argument 2 of 'video_usercopy' makes integer from pointer without a cast
> > drivers/staging/go7007/go7007-v4l2.c:1338: warning: passing argument 4 of 'video_usercopy' makes pointer from integer without a cast
> > drivers/staging/go7007/go7007-v4l2.c:1338: error: too many arguments to function 'video_usercopy'
> >
> > Caused by commit 579209181bfc24ee03a0d167bdc32106afd4e269 ("V4L/DVB
> > (9503): v4l: remove inode argument from video_usercopy") which missed the
> > above driver.
> >
> > I have dropped your tree again for today.
>
> Is it really fair to drop the v4l tree when it was -staging that broke? I'd humbly
> suggest that staging be weighted somewhat lower than the other trees.
I agree, please always drop the staging tree, not any "real" tree :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-07 20:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 3:30 linux-next: v4l-dvb tree build failure Stephen Rothwell
2008-11-07 17:43 ` Harvey Harrison
2008-11-07 18:41 ` Greg KH [this message]
2008-11-07 23:02 ` Stephen Rothwell
2008-11-12 0:54 ` Mauro Carvalho Chehab
2008-11-12 22:45 ` Greg KH
2008-11-07 22:59 ` Stephen Rothwell
2008-11-07 23:06 ` Greg KH
2008-11-08 3:05 ` Sam Ravnborg
2008-11-08 4:38 ` Greg KH
2008-11-08 5:08 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 6:59 Stephen Rothwell
2010-01-27 23:24 ` Andy Walls
2010-01-28 1:54 ` Mauro Carvalho Chehab
2010-01-28 5:24 ` Stephen Rothwell
2009-04-07 0:58 Stephen Rothwell
2009-04-07 1:20 ` Mauro Carvalho Chehab
2009-04-07 4:47 ` Stephen Rothwell
2009-03-27 0:40 Stephen Rothwell
2009-03-27 11:28 ` Mauro Carvalho Chehab
2009-03-27 14:03 ` Stephen Rothwell
2009-03-05 0:35 Stephen Rothwell
2009-03-05 21:51 ` Mauro Carvalho Chehab
2009-03-06 0:05 ` Stephen Rothwell
2009-03-06 1:15 ` Mauro Carvalho Chehab
2009-03-02 0:05 Stephen Rothwell
2009-03-02 0:08 ` Michael Krufky
2009-03-02 0:30 ` Stephen Rothwell
2009-03-02 2:52 ` Mauro Carvalho Chehab
2008-12-08 2:07 Stephen Rothwell
2008-12-01 23:37 Stephen Rothwell
2008-12-02 10:03 ` Mauro Carvalho Chehab
2008-12-02 22:23 ` Stephen Rothwell
2008-12-03 22:48 ` Mauro Carvalho Chehab
2008-12-03 0:08 ` Stephen Rothwell
2008-12-03 22:49 ` Mauro Carvalho Chehab
2008-11-25 4:41 Stephen Rothwell
2008-10-29 2:20 Stephen Rothwell
2008-10-29 12:26 ` Andreas Oberritter
2008-11-03 1:52 ` Stephen Rothwell
2008-11-05 1:57 ` Stephen Rothwell
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=20081107184148.GA2320@kroah.com \
--to=greg@kroah.com \
--cc=harvey.harrison@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.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.