Bruce Ashfield <[email protected]> writes: > Following up on this old patch .. since it causing a problem with my > introduction of > the 4.10 kernel. > > I'm going to have to switch back to the git fetching of lttng to easily > pull in the latest > changes to adapt to the 4.10 kernel.
I don't see why. Support for 4.10 has been in lttng-modules' stable-2.9 branch since January, and is included in the v2.9.1 release, which was tagged a week ago, right before the 4.10 release. I had intended to send the update for lttng-modules on Monday but since I've got it ready I'll send it in a few minutes. You should not need to use lttng-modules' master branch to work with released Linux versions. > lttng just doesn't release often enough for bleeding edge kernels, That's not my impression at all. The LTTng project diligently tracks upstream kernel development and ensures that the latest stable branch of lttng-modules supports the latest released kernel. > while maintaining > a set of patches on top of the released version is possible .. I don't see > the point. Maintaining a set of patches on top of the released version of lttng-modules should not be necessary. > I missed the discussion on this one when it first came out, so I missed the > reason that > we switched away from git to the release tarballs ? I know there's a diversity of opinion on the subject in general, but in the absence of a need to use git, I think using a release tarball should be preferred. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
