linux-kernel - Re: [Ksummit-2008-discuss] Request for discussion on when to merge drivers

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:	Wed, 18 Jun 2008 15:38:55 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Request for discussion on when to merge
 drivers

On Wed, 18 Jun 2008 10:27:46 -0500
James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> I think the Kernel Summit would be a good place to have a discussion of
> what the criteria are for merging a driver (even if, in the end, it's at
> the discretion of the subsystem maintainers).

I agree.

> So perhaps in addition we should be
> encouraging maintainers to run staging branches under similar rules in
> the staging tree, but allowing inclusion into linux-next?

This seems a good idea for drivers.

One potencial issue that we may discuss is some sort of policy on how to deal
with drivers at the "generic" staging tree versus a subsystem maintainer
staging tree. I can foresee a few troubles if a maintainer have such tree, like:

	- After the fixes at -staging, the patch may be kept for a while at
maintainer's staging tree. So, the workflow will be longer than having just one tree;

	- Two different patches for the same device can be sent to the
"generic" staging and to the maintainer's staging tree. So, a conflict will
rise (hopefully detected at linux-next, but may require additional checks for
conflicts with PCI/USB ID's);

On the other hand, without the maintainer's staging tree, this would mean that
the maintainer would have to send their cooking drivers to the generic tree,
with doesn't seem to be very productive.

A possible solution would be if each maintainer with such staging tree would
keep the wiki at linux driver project updated, but this adds some additional
tasks to the maintainer's arms.

Cheers,
Mauro
--
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/