lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 29 Nov 2012 00:04:19 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Hans Verkuil <hverkuil@...all.nl>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org,
	DLOS <davinci-linux-open-source@...ux.davincidsp.com>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Prabhakar Lad <prabhakar.lad@...com>,
	Hans Verkuil <hansverk@...co.com>,
	Prabhakar Lad <prabhakar.csengg@...il.com>,
	Sakari Ailus <sakari.ailus@....fi>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Hans Verkuil <hans.verkuil@...co.com>,
	Manjunath Hadli <manjunath.hadli@...com>,
	LMML <linux-media@...r.kernel.org>
Subject: Re: [PATCH v3 0/9] Media Controller capture driver for DM365

On Wed, Nov 28, 2012 at 08:18:20PM +0100, Hans Verkuil wrote:
> but in this case it just seems to introduce a second
> merge window before the 'real' merge window.
> 

I don't care about this driver, but I mean yes.  That's the point of
linux-next.

I would say the standard rule is that it should sit in linux-next
for a week.  If I submitted a one line bugfix, normally that sits in
linux-next for a week before going upstream.

What frustrates me is that last merge window someone merged a driver
into linux-next for one day.  I submitted a memory corruption fix
the very next day but the maintainer said my fix arrived too late
for the 3.7 release.  What's the point of sending it to linux-next
if you don't have time to take feedback?  So yes, this thread is
mostly me still being cross about that.  :P

We were all expecting Linus to release the kernel last week so no
one should have expected to merge new drivers this week anyway.

regards,
dan carpenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ