On 7/18/25 07:08, Nicola Vetrini wrote:
> On 2025-07-18 11:28, Dmytro Prokopchuk1 wrote:
>> On 7/18/25 12:17, Dmytro Prokopchuk wrote:
>>>
>>>
>>> On 7/18/25 08:31, Jan Beulich wrote:
On 17.07.2025 22:47, Dmytro Prokopchuk1 wrote:
>
>
> On 4/23/25 20:54, victorm.l...@amd.com wrote:
On 2025-07-18 11:28, Dmytro Prokopchuk1 wrote:
On 7/18/25 12:17, Dmytro Prokopchuk wrote:
On 7/18/25 08:31, Jan Beulich wrote:
On 17.07.2025 22:47, Dmytro Prokopchuk1 wrote:
On 4/23/25 20:54, victorm.l...@amd.com wrote:
From: Nicola Vetrini
MISRA C Rules 21.1 ("#define and #undef shall
On 18.07.2025 11:17, Dmytro Prokopchuk1 wrote:
> On 7/18/25 08:31, Jan Beulich wrote:
>> On 17.07.2025 22:47, Dmytro Prokopchuk1 wrote:
>>> I tried to play with Rule 21.1 deviations.
>>>
>>> After applying the following configurations:
>>>
>>> -config=MC3A2.R21.1,macros+={safe, "^offsetof$ || ^(is|
On 7/18/25 12:17, Dmytro Prokopchuk wrote:
>
>
> On 7/18/25 08:31, Jan Beulich wrote:
>> On 17.07.2025 22:47, Dmytro Prokopchuk1 wrote:
>>>
>>>
>>> On 4/23/25 20:54, victorm.l...@amd.com wrote:
From: Nicola Vetrini
MISRA C Rules 21.1 ("#define and #undef shall not be used on a
>
On 7/18/25 08:31, Jan Beulich wrote:
> On 17.07.2025 22:47, Dmytro Prokopchuk1 wrote:
>>
>>
>> On 4/23/25 20:54, victorm.l...@amd.com wrote:
>>> From: Nicola Vetrini
>>>
>>> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
>>> reserved identifier or reserved macro name") and R21.2
On 17.07.2025 22:47, Dmytro Prokopchuk1 wrote:
>
>
> On 4/23/25 20:54, victorm.l...@amd.com wrote:
>> From: Nicola Vetrini
>>
>> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
>> reserved identifier or reserved macro name") and R21.2 ("A reserved
>> identifier or reserved macro n
On 4/23/25 20:54, victorm.l...@amd.com wrote:
> From: Nicola Vetrini
>
> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
> reserved identifier or reserved macro name") and R21.2 ("A reserved
> identifier or reserved macro name shall not be declared") violations
> are not problema
On 2025-07-02 11:55, Dmytro Prokopchuk1 wrote:
Hello, Nicola!
Would you mind if I take part of your patch (related to MISRA C Rule
21.1) and upstream it?
BR, Dmytro.
Hi Dmytro,
I don't mind, though some concerns were raised about the current form of
the patch (see in particular the last em
Hello, Nicola!
Would you mind if I take part of your patch (related to MISRA C Rule
21.1) and upstream it?
BR, Dmytro.
On 4/23/25 20:54, victorm.l...@amd.com wrote:
> From: Nicola Vetrini
>
> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
> reserved identifier or reserved macr
On 2025-04-28 11:04, Jan Beulich wrote:
On 28.04.2025 10:09, Nicola Vetrini wrote:
On 2025-04-28 08:15, Jan Beulich wrote:
On 25.04.2025 17:53, Nicola Vetrini wrote:
On 2025-04-25 10:07, Jan Beulich wrote:
On 24.04.2025 23:45, Stefano Stabellini wrote:
On Thu, 24 Apr 2025, Jan Beulich wrote:
On 28.04.2025 10:09, Nicola Vetrini wrote:
> On 2025-04-28 08:15, Jan Beulich wrote:
>> On 25.04.2025 17:53, Nicola Vetrini wrote:
>>> On 2025-04-25 10:07, Jan Beulich wrote:
On 24.04.2025 23:45, Stefano Stabellini wrote:
> On Thu, 24 Apr 2025, Jan Beulich wrote:
>> On 23.04.2025 19:54
On 2025-04-28 08:15, Jan Beulich wrote:
On 25.04.2025 17:53, Nicola Vetrini wrote:
On 2025-04-25 10:07, Jan Beulich wrote:
On 24.04.2025 23:45, Stefano Stabellini wrote:
On Thu, 24 Apr 2025, Jan Beulich wrote:
On 23.04.2025 19:54, victorm.l...@amd.com wrote:
From: Nicola Vetrini
MISRA C Ru
On 25.04.2025 17:53, Nicola Vetrini wrote:
> On 2025-04-25 10:07, Jan Beulich wrote:
>> On 24.04.2025 23:45, Stefano Stabellini wrote:
>>> On Thu, 24 Apr 2025, Jan Beulich wrote:
On 23.04.2025 19:54, victorm.l...@amd.com wrote:
> From: Nicola Vetrini
>
> MISRA C Rules 21.1 ("#defi
On 2025-04-25 10:07, Jan Beulich wrote:
On 24.04.2025 23:45, Stefano Stabellini wrote:
On Thu, 24 Apr 2025, Jan Beulich wrote:
On 23.04.2025 19:54, victorm.l...@amd.com wrote:
From: Nicola Vetrini
MISRA C Rules 21.1 ("#define and #undef shall not be used on a
reserved identifier or reserved
On 24.04.2025 23:45, Stefano Stabellini wrote:
> On Thu, 24 Apr 2025, Jan Beulich wrote:
>> On 23.04.2025 19:54, victorm.l...@amd.com wrote:
>>> From: Nicola Vetrini
>>>
>>> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
>>> reserved identifier or reserved macro name") and R21.2 ("
On Thu, 24 Apr 2025, Jan Beulich wrote:
> On 23.04.2025 19:54, victorm.l...@amd.com wrote:
> > From: Nicola Vetrini
> >
> > MISRA C Rules 21.1 ("#define and #undef shall not be used on a
> > reserved identifier or reserved macro name") and R21.2 ("A reserved
> > identifier or reserved macro name
On 23.04.2025 19:54, victorm.l...@amd.com wrote:
> From: Nicola Vetrini
>
> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
> reserved identifier or reserved macro name") and R21.2 ("A reserved
> identifier or reserved macro name shall not be declared") violations
> are not problem
On Wed, 23 Apr 2025, victorm.l...@amd.com wrote:
> From: Nicola Vetrini
>
> MISRA C Rules 21.1 ("#define and #undef shall not be used on a
> reserved identifier or reserved macro name") and R21.2 ("A reserved
> identifier or reserved macro name shall not be declared") violations
> are not problem
From: Nicola Vetrini
MISRA C Rules 21.1 ("#define and #undef shall not be used on a
reserved identifier or reserved macro name") and R21.2 ("A reserved
identifier or reserved macro name shall not be declared") violations
are not problematic for Xen, as it does not use the C or POSIX
libraries.
X
19 matches
Mail list logo