Hi all, Here's some important info regarding posted patches and the upcoming merge window. UPCOMING MERGE WINDOW Just to remind everybody, we want to have our omap patches reviewed and queued into for-next by -rc6. That is less than two weeks from today. If you have a larger set of patches, please set them up into a git branch after review for pulling. Please remember that anything touching arch/arm/*omap*/ must be also reviewed on the linux-arm-kernel list, so Cc that list too so I don't have to repost the patches before applying. Basically see the instructions here (server currently down?): http://www.elinux.org/OMAP_patch_merging_process POSTED PATCHES AND PATCHWORK To cope with the patch overload, I added all the patchwork patches into archived-v2.6.35 bundle when v2.6.35 got tagged: http://patchwork.kernel.org/bundle/tmlind/archived-v2.6.35/?archive=both However, at that point the patchwork instance on kernel.org was buggy, and I could not mark them all archived. Anyways, I've marked them all archived now. This means they do not appear as new patches any longer, and patchwork.kernel.org is usable again for tracking what's already queued up. I plan on archiving everything when a new major release comes out, maybe even after some -rc releases if necessary. So the current list of patches we're working with for the upcoming merge window is: http://patchwork.kernel.org/project/linux-omap/list/ Please everybody, check if your patch got archived, and if so, repost as needed against v2.6.36-rc4. In general, if something got archived, please don't consider it rejected. It just means that you have to repost, fix and complain until the patch is ready and integrated :) The standard Linux way you know. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
