> Merged to standard/base (and then propagated out to all BSP branches). > Keep an eye out for issues, but since this is mainline code, it is safe for > all > boards (i.e. not used), so nothing should go wrong :)
Just want to clarify the practice below because it does conflicts with my understand on linux-yocto only merges commits from -stable branch. Is this true that with intel common kernel, standard/base is now accepting patches of type: (1) in-queue for mainline (2) yet to be in-queue for mainline. Question to clarify on what is happening here on v3.14 standard/base: 1) Will the patches in-flight for mainline be eventually cherry-picked back to v3.14 -stable branch? The reason that I ask is, if someone does, I assume that these patches which are now merged into standard/base be dropped/updated with the commit back-ported into v3.14-stable branch? 2) Why the patches not in-flight to mainline be lined-up on feature or machine branch, then be merged into standard/base? Are these patches will be -- _______________________________________________ linux-yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/linux-yocto
