Pkshih <pkshih@xxxxxxxxxxx> writes: >> My recommendation is to avoid accumulating patches at all cost and start >> submitting them as soon as you can. This way you get patches committed >> much more smoother. So do not wait until _all_ patches are ready, >> instead start submitting patches as soon as you have _some_ patches >> ready. In other words, keep the delta between mainline and your >> not-yet-submitted patches as small as possible. >> >> And the patches don't need to be bug free as you can always fix bugs >> later. Just mention in the commit logs that this is preparation for some >> new feature and not fully tested yet. We do that all the time, for >> example Intel's iwlwifi has support for hardware which have not reached >> customers yet. >> > > Thanks for your answer. I'll submit patches when the drivers are ready and > stable. I have another question about the rules of new files. If I want to > add some new files, could I send a big patch with all new files? Is there > any limit? The only limit I know is the byte size limit in the mailing list. When submitting a new driver some people split the driver to one file per patch for easier review but the final commit needs to be one big patch with all files included. If you are adding big files to rtlwifi I think you could try to follow the same model. -- Kalle Valo _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
