<snip> >>Arnd, do we have this documented somewhere for new maintainers to >>follow? > > I would add a few things that we had to go through before for Broadcom SoCs: > > - send your pull requests to a...@kernel.org and copy Arnd, Olof and Kevin > > - you would want to get your PGP key signed by as many people as people as > possible which should not be a problem if you are in an area with lots of > kernel people like the Bay Area (which reminds me I should do that) > > - if you are going to be reasonably active every cycle consider getting a > kernel.org account to host your tree (we are still not doing that...) > > - for future pull requests, you might want to break them into e.g: DTS, > board/Kconfig, drivers, defconfig, maintainers file, and have as little > dependencies between each branch to minimize merge conflicts > > - build test and run test your changes against at least one other platform, > e.g: QEMU to check for multiplatform issues > > In case this is of any value, there is a script here that will automatically > generate pull requests emails for you based on branches matching what was > mentioned above, it will also take care of CC'ing the people involved in the > different patches: > > https://github.com/ffainelli/misc-scripts/blob/master/gen-pull.pl > > It still requires you to create an appropriate tag for the pull requests, > though I might semi-automate that in the future, at least spawn an editor and > offer some guidance, based on commit messages as to what should be in the > pull request email/tag. > > HTH > > -- > Florian
Thanks Florian, this was extremely helpful!
