public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sunil V L" <sunilvl@ventanamicro.com>
To: Gavin Xue <gavin.xue@intel.com>
Cc: devel@edk2.groups.io,
	Andrei Warkentin <andrei.warkentin@intel.com>,
	Yimin Wang <yimin.wang@intel.com>,
	Alan Sheng <alan.sheng@intel.com>
Subject: Re: [edk2 PATCH] MdePkg: Use same ProcessorBind symbol define for RISCV64
Date: Fri, 16 Jun 2023 16:05:57 +0530	[thread overview]
Message-ID: <ZIw7DVomUn50XHCM@sunil-laptop> (raw)
In-Reply-To: <20230616072257.1989-1-gavin.xue@intel.com>

On Fri, Jun 16, 2023 at 03:22:57PM +0800, Gavin Xue wrote:
> Different symbol (PROCESSOR_BIND_H__) define in RISCV64 ProcessorBinding.h
> from other CPU Arch. An unexception compilation error generated
> if include __PROCESSOR_BIND_H__ symbol in header file for
> cross-platform compiling.
> 
> Cc: Andrei Warkentin <andrei.warkentin@intel.com>
> Cc: Sunil V L <sunilvl@ventanamicro.com>
> Cc: Yimin Wang <yimin.wang@intel.com>
> Cc: Alan Sheng <alan.sheng@intel.com>
> Signed-off-by: Gavin Xue <gavin.xue@intel.com>
> ---
>  MdePkg/Include/RiscV64/ProcessorBind.h | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/MdePkg/Include/RiscV64/ProcessorBind.h b/MdePkg/Include/RiscV64/ProcessorBind.h
> index 1d42d92de4..7f24e77b8c 100644
> --- a/MdePkg/Include/RiscV64/ProcessorBind.h
> +++ b/MdePkg/Include/RiscV64/ProcessorBind.h
> @@ -2,13 +2,14 @@
>    Processor or Compiler specific defines and types for RISC-V
>  
>    Copyright (c) 2016 - 2020, Hewlett Packard Enterprise Development LP. All rights reserved.<BR>
> +  Copyright (c) 2023, Intel Corporation. All rights reserved.<BR>
>  
>    SPDX-License-Identifier: BSD-2-Clause-Patent
>  
>  **/
>  
> -#ifndef PROCESSOR_BIND_H__
> -#define PROCESSOR_BIND_H__
> +#ifndef __PROCESSOR_BIND_H__
> +#define __PROCESSOR_BIND_H__
>  
As per EDK2 coding standards, the include guard names should not
start with _. So, I guess you need to fix the header files of other
architectures which are using _ in their include guard.

Thanks,
Sunil

  reply	other threads:[~2023-06-16 10:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  7:22 [edk2 PATCH] MdePkg: Use same ProcessorBind symbol define for RISCV64 Gavin Xue
2023-06-16 10:35 ` Sunil V L [this message]
2023-06-16 14:11   ` [edk2-devel] " Pedro Falcato
2023-06-16 15:51     ` Xue, Gavin
2023-06-21 14:16       ` Pedro Falcato
2023-06-22  9:58         ` Xue, Gavin
2023-06-22 15:45           ` Pedro Falcato
2023-06-27 20:29           ` Michael D Kinney
2023-06-30  9:28             ` Xue, Gavin
2023-06-30 16:59               ` Michael D Kinney
2023-07-03  9:01                 ` Xue, Gavin
2023-07-03 17:01                 ` Pedro Falcato
2023-07-04  9:39                   ` Xue, Gavin

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-list 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=ZIw7DVomUn50XHCM@sunil-laptop \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox