Messages in this thread | | | Date | Wed, 18 Jun 2008 15:38:55 -0300 | From | Mauro Carvalho Chehab <> | 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@HansenPartnership.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
| |