On 2018-02-05 15:17:56 [-0600], Dan Murphy wrote: > We are catching warnings and errors with these defconfigs. I have reported 2 warnings but > I have not received a response. I guess I should report these to this list as opposed to the maintainers. You reported two warnings to my private address while I was traveling. The usual workflow for reporting is to send this to the mailing list and Cc the RT maintainer(s) (which would contain the email address I am using right now). > We have a "next" process that runs nightly that merges in the stable rc candidate into our branch > so we can anticipate if the new stable or TI developer branches will cause a merge conflict when merged into our branch sets. > > For instance 4.14.17 stable rc caused a merge conflict in the hrtimer.c file. This became a known issue as soon as the stable rc was > available. The RT 4.14 upstream branch is currently on 4.14.15 so now our RT branch is blocked from receiving a new stable until the > RT upstream branch is updated. I usually do a new release once I have something in my pipe or if people ask to update new stable due to $reason. > Dan Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
