On Wed, Mar 08, 2017 at 02:55:44PM +0100, Hans Verkuil wrote: > On 08/03/17 14:45, Hans Verkuil wrote: > > On 08/03/17 14:39, Greg KH wrote: > > > On Wed, Mar 08, 2017 at 01:49:23PM +0100, Hans Verkuil wrote: > > > > OK, so I discovered that these patches are for a driver added to linux-next > > > > without it ever been cross-posted to linux-media. > > > > > > > > To be polite, I think that's rather impolite. > > > > > > They were, but got rejected due to the size :( > > > > > > Mauro was cc:ed directly, he knew these were coming... > > > > > > I can take care of the cleanup patches for now, you don't have to review > > > them if you don't want to. > > > > Please do. > > > > For the next time if the patches are too large: at least post a message with > > a link to a repo for people to look at. I would like to know what's going > > on in staging/media, especially since I will do a lot of the reviewing (at > > least if it is a V4L2 driver) when they want to move it out of staging. > > Same issue BTW with the bcm2835 driver. That too landed in staging without > ever being posted to the linux-media mailinglist. Size is no excuse for that > driver since it isn't that large. > > I'll handle cleanup patches for the bcm2835 driver since it is now in our tree. Nope, it got moved out as it didn't belong there yet :) It's now in drivers/staging/vc04_services/ as all of the issues so far aren't media ones, but vc04 api issues. Once those get ironed out, then the media people can have at it :) thanks, greg k-h
