On Sun, Sep 16, 2012 at 8:42 PM, Sujith Manoharan <c_manoha@xxxxxxxxxxxx> wrote: > Hi, > > These patches are for the 3.6.y branch in compat-drivers. > > Sujith > > Sujith Manoharan (3): > compat-drivers: Add pending stable patches > compat-drivers: Add new cherry picked patches > compat-drivers: Add linux-next pending patches Great thanks, applied and pushed! v3.6-rc6 was pushed out recently as well, and I updated the trees to reflect that. Based on that and your patches I've kicked out a new set of first tarballs based on v3.6-rc1. These releases did not have any pending-stable/ patches as in between v3.6-rc6..next-20120917 and as such there are no "-s" releases. http://www.orbit-lab.org/kernel/compat-wireless-3-stable/v3.6/compat-wireless-3.6-rc6-1.tar.bz2 http://www.orbit-lab.org/kernel/compat-wireless-3-stable/v3.6/compat-wireless-3.6-rc6-1-n.tar.bz2 http://www.orbit-lab.org/kernel/compat-wireless-3-stable/v3.6/compat-wireless-3.6-rc6-1-np.tar.bz2 http://www.orbit-lab.org/kernel/compat-wireless-3-stable/v3.6/compat-wireless-3.6-rc6-1-npc.tar.bz2 Legend Extra flag meanings: -s - get and apply pending-stable/ from linux-next.git -n - apply the patches linux-next-cherry-picks/ directory -p - apply the patches on the linux-next-pending/ directory -c - apply the patches on the crap/ directory When no flags are used it means a vanilla release with 0 delta. The respective ckmake logs for all releases will be uploaded in about 2-3 hours, but before tagging a release I did run ckmake test against the -snpc release and everything went fine so I don't suspect issues with the rest of the releases. I should note that v3.6 releases will be the last set of release hosted on orbit-lab.org and named as compat-wireless, after this, as of v3.7, releases will be hosted on kernel.org and branded under compat-drivers. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
