> On 26 Oct 2022, at 13:06, Jan Beulich wrote:
>
> On 25.10.2022 12:13, Luca Fancellu wrote:
>> Here is an example to add a new justification in safe.json::
>>
>> |{
>> |"version": "1.0",
>> |"content": [
>> |{
>> |"id":"SAF-0-safe",
>> |"analyser": {
>>
On 25.10.2022 12:13, Luca Fancellu wrote:
> Here is an example to add a new justification in safe.json::
>
> |{
> |"version": "1.0",
> |"content": [
> |{
> |"id":"SAF-0-safe",
> |"analyser": {
> |"cppcheck": "misra-c2012-20.7",
> |
> On 26 Oct 2022, at 10:36, Julien Grall wrote:
>
>
>
> On 25/10/2022 11:13, Luca Fancellu wrote:
>> Hi all,
>
> Hi Luca,
>
> Some comments below if we plan to merge the doc in the tree.
>
>> This is the V2 of the proposal for deviations tagging in the Xen codebase,
>> this includes
>> al
On 25/10/2022 11:13, Luca Fancellu wrote:
Hi all,
Hi Luca,
Some comments below if we plan to merge the doc in the tree.
This is the V2 of the proposal for deviations tagging in the Xen codebase, this
includes
all the feedbacks from the FuSa session held at the Xen Summit 2022 and all the
> On 26 Oct 2022, at 00:24, Stefano Stabellini wrote:
>
> On Tue, 25 Oct 2022, Luca Fancellu wrote:
>> Hi all,
>>
>> This is the V2 of the proposal for deviations tagging in the Xen codebase,
>> this includes
>> all the feedbacks from the FuSa session held at the Xen Summit 2022 and all
>> t
On Tue, 25 Oct 2022, Luca Fancellu wrote:
> Hi all,
>
> This is the V2 of the proposal for deviations tagging in the Xen codebase,
> this includes
> all the feedbacks from the FuSa session held at the Xen Summit 2022 and all
> the
> feedbacks received in the previous proposal sent on the mailing
Hi all,
This is the V2 of the proposal for deviations tagging in the Xen codebase, this
includes
all the feedbacks from the FuSa session held at the Xen Summit 2022 and all the
feedbacks received in the previous proposal sent on the mailing list.
Here a link to the previous thread:
https://list
On 19.10.2022 09:52, Bertrand Marquis wrote:
>> On 19 Oct 2022, at 07:38, Jan Beulich wrote:
>> On 18.10.2022 18:11, Bertrand Marquis wrote:
On 18 Oct 2022, at 16:29, Jan Beulich wrote:
On 18.10.2022 17:17, Luca Fancellu wrote:
>> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
>>
> On 19 Oct 2022, at 07:38, Jan Beulich wrote:
>
> On 18.10.2022 18:11, Bertrand Marquis wrote:
>>> On 18 Oct 2022, at 16:29, Jan Beulich wrote:
>>> On 18.10.2022 17:17, Luca Fancellu wrote:
> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
> On 13.10.2022 12:11, Luca Fancellu wrote:
>>>
Hi Jan,
> On 19 Oct 2022, at 07:38, Jan Beulich wrote:
>
> On 18.10.2022 18:11, Bertrand Marquis wrote:
>>> On 18 Oct 2022, at 16:29, Jan Beulich wrote:
>>> On 18.10.2022 17:17, Luca Fancellu wrote:
> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
> On 13.10.2022 12:11, Luca Fancellu wro
On 18.10.2022 18:11, Bertrand Marquis wrote:
>> On 18 Oct 2022, at 16:29, Jan Beulich wrote:
>> On 18.10.2022 17:17, Luca Fancellu wrote:
On 13 Oct 2022, at 12:34, Jan Beulich wrote:
On 13.10.2022 12:11, Luca Fancellu wrote:
>> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
>> On
Hi,
> On 18 Oct 2022, at 16:29, Jan Beulich wrote:
>
> On 18.10.2022 17:17, Luca Fancellu wrote:
>>> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
>>> On 13.10.2022 12:11, Luca Fancellu wrote:
> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
> On 12.10.2022 18:00, Luca Fancellu wrote:
>>>
On 18.10.2022 17:49, Luca Fancellu wrote:
>> On 18 Oct 2022, at 16:29, Jan Beulich wrote:
>> On 18.10.2022 17:17, Luca Fancellu wrote:
On 13 Oct 2022, at 12:34, Jan Beulich wrote:
On 13.10.2022 12:11, Luca Fancellu wrote:
>> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
>> Iirc
> On 18 Oct 2022, at 16:29, Jan Beulich wrote:
>
> On 18.10.2022 17:17, Luca Fancellu wrote:
>>> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
>>> On 13.10.2022 12:11, Luca Fancellu wrote:
> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
> On 12.10.2022 18:00, Luca Fancellu wrote:
>>
On 18.10.2022 17:17, Luca Fancellu wrote:
>> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
>> On 13.10.2022 12:11, Luca Fancellu wrote:
On 13 Oct 2022, at 08:50, Jan Beulich wrote:
On 12.10.2022 18:00, Luca Fancellu wrote:
> Entries in the database should never be removed, even if th
> On 13 Oct 2022, at 12:34, Jan Beulich wrote:
>
> On 13.10.2022 12:11, Luca Fancellu wrote:
>>> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
>>> On 12.10.2022 18:00, Luca Fancellu wrote:
In the Xen codebase, these tags will be used to document and suppress
findings:
- SA
On 13.10.2022 12:11, Luca Fancellu wrote:
>> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
>> On 12.10.2022 18:00, Luca Fancellu wrote:
>>> In the Xen codebase, these tags will be used to document and suppress
>>> findings:
>>>
>>> - SAF-X-safe: This tag means that the next line of code contains a
Hi Jan,
> On 13 Oct 2022, at 08:50, Jan Beulich wrote:
>
> On 12.10.2022 18:00, Luca Fancellu wrote:
>> Documenting violations
>> ==
>
> I expect this is mean to become an in-tree document at some point?
Yes, this will become part of the documentation at some point.
>
>>
On 12.10.2022 18:00, Luca Fancellu wrote:
> Documenting violations
> ==
I expect this is mean to become an in-tree document at some point?
> Static analysers are used on the Xen codebase for both static analysis and
> MISRA
> compliance.
> There might be the need to suppress
Hi all,
Here is a proposal to create a deviation system for all the static analyser
finding from
both generic static code checkers and MISRA compliance, as said before, there
might
be some case where we won’t fix a part of the code because the way it is
written is
safer than the proposed fix fr
20 matches
Mail list logo
