public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Samer El-Haj-Mahmoud" <samer.el-haj-mahmoud@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@nuviainc.com" <rebecca@nuviainc.com>
Cc: Eric Jin <eric.jin@intel.com>,
	G Edhaya Chandran <Edhaya.Chandran@arm.com>,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [edk2-devel] [edk2-test] [PATCH 3/3] uefi-sct/SctPkg: Fix some indentation issues in build.sh
Date: Wed, 11 Nov 2020 21:17:21 +0000	[thread overview]
Message-ID: <DB7PR08MB32603AE4242DA070FC2477B790E80@DB7PR08MB3260.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200924212131.22982-3-rebecca@nuviainc.com>

Reviewed-By: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca
> Cran via groups.io
> Sent: Thursday, September 24, 2020 5:22 PM
> To: devel@edk2.groups.io
> Cc: Eric Jin <eric.jin@intel.com>; G Edhaya Chandran
> <Edhaya.Chandran@arm.com>; Samer El-Haj-Mahmoud <Samer.El-Haj-
> Mahmoud@arm.com>; Rebecca Cran <rebecca@nuviainc.com>
> Subject: [edk2-devel] [edk2-test] [PATCH 3/3] uefi-sct/SctPkg: Fix some
> indentation issues in build.sh
>
> build.sh contains a mixture of tabs and spaces, with differing numbers of
> spaces used for indents. Update it so any single block only uses one style of
> indentation.
>
> Signed-off-by: Rebecca Cran <rebecca@nuviainc.com>
> ---
>  uefi-sct/SctPkg/build.sh | 33 ++++++++++++++++-----------------
>  1 file changed, 16 insertions(+), 17 deletions(-)
>
> diff --git a/uefi-sct/SctPkg/build.sh b/uefi-sct/SctPkg/build.sh index
> be610deb..37667711 100755
> --- a/uefi-sct/SctPkg/build.sh
> +++ b/uefi-sct/SctPkg/build.sh
> @@ -56,9 +56,9 @@ function get_gcc_version  {
>  gcc_version=$($1 -dumpversion)
>
> -    if [ ${gcc_version%%.*} -gt 5 ]; then
> -        gcc_version=5
> -    fi
> +if [ ${gcc_version%%.*} -gt 5 ]; then
> +gcc_version=5
> +fi
>
>  case $gcc_version in
>  4.6*|4.7*|4.8*|4.9*|5*)
> @@ -152,10 +152,9 @@ case `uname` in
>  ;;
>
>  GCC* | gcc*)
> -            set_cross_compile
> -        CROSS_COMPILE="$TEMP_CROSS_COMPILE"
> -            export TARGET_TOOLS=`get_gcc_version "$CROSS_COMPILE"gcc`
> -
> +set_cross_compile
> +CROSS_COMPILE="$TEMP_CROSS_COMPILE"
> +export TARGET_TOOLS=`get_gcc_version
> "$CROSS_COMPILE"gcc`
>  ;;
>
>  *)
> @@ -224,7 +223,7 @@ then
>    status=$?
>    if test $status -ne 0
>    then
> -  echo Error while building EDK tools
> +    echo Error while building EDK tools
>      exit -1
>    fi
>  else
> @@ -239,7 +238,7 @@ make -C SctPkg/Tools/Source/GenBin  status=$?
>  if test $status -ne 0
>  then
> -echo Error while building GenBin
> +  echo Error while building GenBin
>    exit -1
>  fi
>
> @@ -258,8 +257,8 @@ build -p SctPkg/UEFI/UEFI_SCT.dsc -a
> $SCT_TARGET_ARCH -t $TARGET_TOOLS -b $SCT_B  status=$?
>  if test $status -ne 0
>  then
> -echo Could not build the UEFI SCT package
> -        exit -1
> +  echo Could not build the UEFI SCT package  exit -1
>  fi
>
>  build -p SctPkg/UEFI/IHV_SCT.dsc -a $SCT_TARGET_ARCH -t
> $TARGET_TOOLS -b $SCT_BUILD $3 $4 $5 $6 $7 $8 $9
> @@ -268,8 +267,8 @@ build -p SctPkg/UEFI/IHV_SCT.dsc -a
> $SCT_TARGET_ARCH -t $TARGET_TOOLS -b $SCT_BU
>  status=$?
>  if test $status -ne 0
>  then
> -echo Could not build the IHV SCT package
> -        exit -1
> +  echo Could not build the IHV SCT package
> +  exit -1
>  fi
>
>
> @@ -299,8 +298,8 @@ pwd
>  status=$?
>  if test $status -ne 0
>  then
> -echo Could not generate UEFI SCT binary
> -     exit -1
> +  echo Could not generate UEFI SCT binary
> +  exit -1
>  else
>  echo The SCT binary "SctPackage${SCT_TARGET_ARCH}" is located at
> "$EFI_SOURCE/Build/UefiSct/${SCT_BUILD}_${TARGET_TOOLS}"
>  fi
> @@ -315,8 +314,8 @@ pwd
>  status=$?
>  if test $status -ne 0
>  then
> -echo Could not generate IHV SCT binary
> -     exit -1
> +  echo Could not generate IHV SCT binary
> +  exit -1
>  else
>  echo The IHV binary "SctPackage${SCT_TARGET_ARCH}" is located at
> "$EFI_SOURCE/Build/IhvSct/${SCT_BUILD}_${TARGET_TOOLS}"
>  fi
> --
> 2.26.2
>
>
>
> -=-=-=-=-=-=
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#65579): https://edk2.groups.io/g/devel/message/65579
> Mute This Topic: https://groups.io/mt/77067562/1945644
> Group Owner: devel+owner@edk2.groups.io
> Unsubscribe: https://edk2.groups.io/g/devel/unsub [samer.el-haj-
> mahmoud@arm.com]
> -=-=-=-=-=-=
>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

      reply	other threads:[~2020-11-11 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 21:21 [edk2-test] [PATCH 1/3] uefi-sct/SctPkg: Fix build.sh when specifying GCC5 toolchain Rebecca Cran
2020-09-24 21:21 ` [edk2-test] [PATCH 2/3] uefi-sct: Fix the mailing list address in Maintainers.txt and Readme.md Rebecca Cran
2020-09-24 21:21 ` [edk2-test] [PATCH 3/3] uefi-sct/SctPkg: Fix some indentation issues in build.sh Rebecca Cran
2020-11-11 21:17   ` Samer El-Haj-Mahmoud [this message]

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=DB7PR08MB32603AE4242DA070FC2477B790E80@DB7PR08MB3260.eurprd08.prod.outlook.com \
    --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