From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>, Wei Liu <wl@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Bertrand Marquis <bertrand.marquis@arm.com>
Subject: Re: [PATCH 1/3] x86/p2m.h: Add include guards
Date: Mon, 9 May 2022 15:18:05 +0200 [thread overview]
Message-ID: <YnkUjVuRZa1EVgLY@Air-de-Roger> (raw)
In-Reply-To: <20220509122409.14184-2-andrew.cooper3@citrix.com>
On Mon, May 09, 2022 at 01:24:07PM +0100, Andrew Cooper wrote:
> Spotted by Eclair MISRA scanner.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Roger Pau Monné <roger.pau@citrix.com>
> CC: Wei Liu <wl@xen.org>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> CC: Julien Grall <julien@xen.org>
> CC: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
> CC: Bertrand Marquis <bertrand.marquis@arm.com>
> ---
> xen/arch/x86/mm/p2m.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/xen/arch/x86/mm/p2m.h b/xen/arch/x86/mm/p2m.h
> index cc0f6766e4df..dc706b8e4799 100644
> --- a/xen/arch/x86/mm/p2m.h
> +++ b/xen/arch/x86/mm/p2m.h
> @@ -15,6 +15,9 @@
> * along with this program; If not, see <http://www.gnu.org/licenses/>.
> */
>
> +#ifndef __ARCH_MM_P2M_H__
> +#define __ARCH_MM_P2M_H__
Do we have any guidelines regarding guard naming? Some files seem to
use __ASM_X86_, others just __ASM and some just _X86.
Thanks, Roger.
next prev parent reply other threads:[~2022-05-09 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:24 [PATCH 0/3] xen: Trivial MISRA fixes Andrew Cooper
2022-05-09 12:24 ` [PATCH 1/3] x86/p2m.h: Add include guards Andrew Cooper
2022-05-09 12:32 ` Bertrand Marquis
2022-05-09 13:18 ` Roger Pau Monné [this message]
2022-05-09 13:23 ` Andrew Cooper
2022-05-17 15:38 ` Jan Beulich
2022-05-17 18:42 ` Roberto Bagnara
2022-05-18 6:26 ` Jan Beulich
2022-05-09 12:24 ` [PATCH 2/3] x86/shadow: Don't use signed bitfield in sh_emulate_ctxt Andrew Cooper
2022-05-09 12:40 ` Bertrand Marquis
2022-05-09 13:19 ` Roger Pau Monné
2022-05-09 12:24 ` [PATCH 3/3] common/spinlock: Drop inline from _spin_lock_cb() Andrew Cooper
2022-05-09 12:34 ` Bertrand Marquis
2022-05-09 13:53 ` Roger Pau Monné
2022-05-17 15:42 ` Jan Beulich
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=YnkUjVuRZa1EVgLY@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.