Tomasz Warniełło <tomasz.warniello@xxxxxxxxx> writes: >> - Post your patch series as a single thread with a coherent cover >> letter. > > Sorry, I'm a newbie in this business. I need to figure out how emails > work. Is this just one thread per version or one thread per all versions? > Can you please direct me to some documentation about this? One thread per version is good; please do not post new versions to old threads. A tool like "git send-email" can be your friend here. See Documentation/process/submitting-patches.rst for lots of details on how to submit patches. Along these lines, I appreciate that you broke up the series as I requested, but you overdid it a bit. Think in terms of logical changes and making things easy to review, and you should be able to coalesce things a bit. >> - Stick with current coding conventions > > To be honest, I need to think this over. Think hard; if you're unable to work with the kernel project's conventions, there's not a lot of point in resubmitting the patches. Thanks, jon
