[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [XEN PATCH 08/10] xen/errno: address violations of MISRA C Rule 20.7
On Thu, 29 Feb 2024, Nicola Vetrini wrote: > MISRA C Rule 20.7 states: "Expressions resulting from the expansion > of macro parameters shall be enclosed in parentheses". Therefore, some > macro definitions should gain additional parentheses to ensure that all > current and future users will be safe with respect to expansions that > can possibly alter the semantics of the passed-in macro parameter. > > No functional change. > > Signed-off-by: Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx> > --- > xen/include/xen/errno.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/xen/include/xen/errno.h b/xen/include/xen/errno.h > index 69b28dd3c6c5..506674701fae 100644 > --- a/xen/include/xen/errno.h > +++ b/xen/include/xen/errno.h > @@ -3,7 +3,7 @@ > > #ifndef __ASSEMBLY__ > > -#define XEN_ERRNO(name, value) name = value, > +#define XEN_ERRNO(name, value) name = (value), I see this and the fact that "name" was not parenthesized and it would deliberate right? So I guess the left side of an assignment doesn't need parenthesis?
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |