From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Julien Grall <julien@xen.org>
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org,
michal.orzel@amd.com, xenia.ragiadakou@amd.com,
ayan.kumar.halder@amd.com, consulting@bugseng.com,
jbeulich@suse.com, andrew.cooper3@citrix.com,
roger.pau@citrix.com, George Dunlap <george.dunlap@citrix.com>,
Wei Liu <wl@xen.org>, Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [XEN PATCH][for-4.19] xen: replace occurrences of SAF-1-safe with asmlinkage attribute
Date: Tue, 07 Nov 2023 11:22:10 +0100 [thread overview]
Message-ID: <8435a92f1a70832abb3215e2630f729f@bugseng.com> (raw)
In-Reply-To: <859bbbc7-617a-4df0-893d-320b7e1e6e5b@xen.org>
On 2023-11-07 10:49, Julien Grall wrote:
> Hi,
>
> On 07/11/2023 08:36, Nicola Vetrini wrote:
>> On 2023-11-06 23:57, Julien Grall wrote:
>>> Hi Nicola,
>>>
>>> On 03/11/2023 18:05, Nicola Vetrini wrote:
>>>> The comment-based justifications for MISRA C:2012 Rule 8.4 are
>>>> replaced
>>>> by the asmlinkage pseudo-attribute, for the sake of uniformity.
>>>> The deviation with a comment based on the SAF framework is also
>>>> mentioned as a last resort.
>>>
>>> I don't see any reason to keep SAF-1 after this patch. So can this be
>>> removed?
>>>
>>
>> In documenting-violations.rst it's stated:
>> "Entries in the database shall never be removed, even if they are not
>> used
>> anymore in the code (if a patch is removing or modifying the faulty
>> line).
>> This is to make sure that numbers are not reused which could lead to
>> conflicts
>> with old branches or misleading justifications."
>
> I read this as the number can not be re-used. But we could replace the
> description with "Not used anymore".
>
>>
>> that's why I kept SAF-1 in the safe.json file and added the remark
>> about it
>> being a last resort.
>
> Right, but this is confusing. What is the last resort? Why would one
> use it? It would be best to not mention SAF-1 at all in deviations.rst.
>
> Cheers,
Ok, I'll submit a v2
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
prev parent reply other threads:[~2023-11-07 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 18:05 [XEN PATCH][for-4.19] xen: replace occurrences of SAF-1-safe with asmlinkage attribute Nicola Vetrini
2023-11-06 22:57 ` Julien Grall
2023-11-07 8:36 ` Nicola Vetrini
2023-11-07 9:49 ` Julien Grall
2023-11-07 10:22 ` Nicola Vetrini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8435a92f1a70832abb3215e2630f729f@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.