From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
alessandro.zucchelli@bugseng.com, simone.ballarin@bugseng.com,
consulting@bugseng.com, andrew.cooper3@citrix.com,
julien@xen.org, roger.pau@citrix.com, bertrand.marquis@arm.com,
michal.orzel@amd.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] misra: increase identifiers length to 64
Date: Mon, 18 Nov 2024 10:55:37 +0100 [thread overview]
Message-ID: <eeaec89c4d4aa8abd738d8af7d068a19@bugseng.com> (raw)
In-Reply-To: <782b24a0-a960-4667-a183-1e270841d2a8@suse.com>
On 2024-11-18 09:58, Jan Beulich wrote:
> On 16.11.2024 01:23, Stefano Stabellini wrote:
>> Currently the identifiers characters limit is arbitrarily set to 40.
>> It
>> causes a few violations as we have some identifiers longer than 40.
>>
>> Increase the limit to another rather arbitrary limit of 64. Thanks to
>> this change, we remove a few violations, getting us one step closer to
>> marking Rules 5.2 and 5.4 as clean.
>>
>> Also update the ECLAIR config that was actually set to 63 as character
>> limit.
>
> What I don't really understand: With the Eclair config already having
> said
> 63, how come we did see patches aiming at dealing with the limit being
> just
> 40? IOW - how would those (supposed) issue even have been spotted.
>
Hi Jan,
the issue was spotted by Andrew, and therefore we made the patches to
align the configuration with the limits chosen by the project, which
makes those violations appear. It is also possibile to do it the other
way around (align the rst with the ECLAIR configuration), which spares
the need for additional deviations.
In that case, I agree that 63 is better than 64.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2024-11-18 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 0:23 [PATCH] misra: increase identifiers length to 64 Stefano Stabellini
2024-11-16 8:59 ` Frediano Ziglio
2024-11-17 15:36 ` Roberto Bagnara
2024-11-18 8:58 ` Jan Beulich
2024-11-18 9:55 ` Nicola Vetrini [this message]
2024-11-18 23:50 ` Stefano Stabellini
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=eeaec89c4d4aa8abd738d8af7d068a19@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=alessandro.zucchelli@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=simone.ballarin@bugseng.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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.