[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Meeting notes from Feb 28 and MISRA C copyright text
On Mon, 7 Mar 2022, Bertrand Marquis wrote: > Hi, > > > On 1 Mar 2022, at 22:09, Stefano Stabellini <stefano.stabellini@xxxxxxxxxx> > > wrote: > > > > Hi all, > > > > As you might recall, we have an outstanding action to finalize the > > format of the list of MISRA C rules for Xen. One of the important > > details to finalize is the MISRA C copyright text at the top of the > > file. > > > > We discussed the topic with David Ward during the Xen FuSa meeting of > > Feb 28. We agreed on the appended text. Thanks David for your help on > > this! > > This is awesome :-) > > I will integrate this in my patch proposal and publish in the next weeks: > - a patch to add cppcheck support to Xen > - a patch to add the Misra text with the new disclaimer > - a patch to add support for Misra cppcheck > > First one, I will submit as normal patch for Xen but I was thinking to submit > the 2 other ones related to Misra as RFC for now as it might generate > discussions. Any other suggestion here ? I agree that the first patch is a normal patch. The third patch is also "normal": there is nothing wrong with adding more checks to cppcheck. For the second patch (the one adding the list of rules), I think we need to be careful to specify that this is not (yet) the list of rules that Xen Project is going to follow: we haven't discussed it yet with the other maintainters. We need to clarify that it is a list of rules we think are relevant to Xen and one day maybe could become part of CODING_STYLE. However, as of now, they are not part of CODING_STYLE and are not enforced. Does it make sense?
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |