Message ID | cover.1721050709.git.federico.serafini@bugseng.com (mailing list archive) |
---|---|
Headers | show |
Series | x86: address some violations of MISRA C Rule 16.3 | expand |
On 15.07.2024 18:48, Federico Serafini wrote: > This patch series fixes a missing escape in a deviation and addresses some > violations. > > Federico Serafini (9): > automation/eclair: fix deviation of MISRA C Rule 16.3 > x86/cpuid: use fallthrough pseudo keyword > x86/domctl: address a violation of MISRA C Rule 16.3 > x86/vpmu: address violations of MISRA C Rule 16.3 > x86/traps: address violations of MISRA C Rule 16.3 > x86/mce: address violations of MISRA C Rule 16.3 > x86/hvm: address violations of MISRA C Rule 16.3 > x86/mm: add defensive return > x86/mpparse: address a violation of MISRA C Rule 16.3 And what exactly was this resend about? Even sent as reply to the original submission, rather than as a plain new thread, thus resulting in everything being mixed up into a single thread? Jan
On 16/07/24 08:59, Jan Beulich wrote: > On 15.07.2024 18:48, Federico Serafini wrote: >> This patch series fixes a missing escape in a deviation and addresses some >> violations. >> >> Federico Serafini (9): >> automation/eclair: fix deviation of MISRA C Rule 16.3 >> x86/cpuid: use fallthrough pseudo keyword >> x86/domctl: address a violation of MISRA C Rule 16.3 >> x86/vpmu: address violations of MISRA C Rule 16.3 >> x86/traps: address violations of MISRA C Rule 16.3 >> x86/mce: address violations of MISRA C Rule 16.3 >> x86/hvm: address violations of MISRA C Rule 16.3 >> x86/mm: add defensive return >> x86/mpparse: address a violation of MISRA C Rule 16.3 > > And what exactly was this resend about? Even sent as reply to the original > submission, rather than as a plain new thread, thus resulting in everything > being mixed up into a single thread? I'm sorry I forgot to add the maintainers in the first patch series, so I resent it.