From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [edk2-devel] [Patch 3/4] ArmVirtPkg: Normalize line endings to CRLF
Date: Thu, 4 Apr 2019 16:55:39 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9C79264@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <5b806211-ee0a-9ed3-44a4-d228925c1976@redhat.com>
Laszlo,
I am doing these before the license change to resolve
PatchCheck.py issues in the license change patch series.
I will rebase before commit.
Mike
> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io]
> On Behalf Of Laszlo Ersek
> Sent: Thursday, April 4, 2019 5:53 AM
> To: devel@edk2.groups.io; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Subject: Re: [edk2-devel] [Patch 3/4] ArmVirtPkg:
> Normalize line endings to CRLF
>
> On 04/04/19 00:00, Michael D Kinney wrote:
> > https://bugzilla.tianocore.org/show_bug.cgi?id=1659
> >
> > Normalize line endings to use CRLF to pass
> PatchCheck.py
> >
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Contributed-under: TianoCore Contribution Agreement
> 1.1
> > Signed-off-by: Michael D Kinney
> <michael.d.kinney@intel.com>
> > ---
> > ArmVirtPkg/Include/Platform/Hidden.h | 56
> ++++++++++++++--------------
> > 1 file changed, 28 insertions(+), 28 deletions(-)
> >
> > diff --git a/ArmVirtPkg/Include/Platform/Hidden.h
> b/ArmVirtPkg/Include/Platform/Hidden.h
> > index fbd3467471..997866ff50 100644
> > --- a/ArmVirtPkg/Include/Platform/Hidden.h
> > +++ b/ArmVirtPkg/Include/Platform/Hidden.h
> > @@ -1,28 +1,28 @@
> > -/** @file
> > -
> > - Copyright (c) 2018, Linaro Limited. All rights
> reserved.
> > -
> > - This program and the accompanying materials
> > - are licensed and made available under the terms and
> conditions of the BSD License
> > - which accompanies this distribution. The full text
> of the license may be found at
> > - http://opensource.org/licenses/bsd-license.php
> > -
> > - THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON
> AN "AS IS" BASIS,
> > - WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND,
> EITHER EXPRESS OR IMPLIED.
> > -
> > -**/
> > -
> > -#ifndef __PLATFORM_HIDDEN_H
> > -#define __PLATFORM_HIDDEN_H
> > -
> > -//
> > -// Setting the GCC -fvisibility=hidden command line
> option is not quite the same
> > -// as setting the pragma below: the former only
> affects definitions, whereas the
> > -// pragma affects extern declarations as well. So if
> we want to ensure that no
> > -// GOT indirected symbol references are emitted, we
> need to use the pragma, or
> > -// GOT based cross object references could be
> emitted, e.g., in libraries, and
> > -// these cannot be relaxed to ordinary symbol
> references at link time.
> > -//
> > -#pragma GCC visibility push (hidden)
> > -
> > -#endif
> > +/** @file
> > +
> > + Copyright (c) 2018, Linaro Limited. All rights
> reserved.
> > +
> > + This program and the accompanying materials
> > + are licensed and made available under the terms and
> conditions of the BSD License
> > + which accompanies this distribution. The full text
> of the license may be found at
> > + http://opensource.org/licenses/bsd-license.php
> > +
> > + THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON
> AN "AS IS" BASIS,
> > + WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND,
> EITHER EXPRESS OR IMPLIED.
> > +
> > +**/
> > +
> > +#ifndef __PLATFORM_HIDDEN_H
> > +#define __PLATFORM_HIDDEN_H
> > +
> > +//
> > +// Setting the GCC -fvisibility=hidden command line
> option is not quite the same
> > +// as setting the pragma below: the former only
> affects definitions, whereas the
> > +// pragma affects extern declarations as well. So if
> we want to ensure that no
> > +// GOT indirected symbol references are emitted, we
> need to use the pragma, or
> > +// GOT based cross object references could be
> emitted, e.g., in libraries, and
> > +// these cannot be relaxed to ordinary symbol
> references at link time.
> > +//
> > +#pragma GCC visibility push (hidden)
> > +
> > +#endif
> >
>
> This will conflict with the license conversion, so I
> suggest redoing
> this patch after the conversion is pushed.
>
> Other than that,
>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
>
> Thanks
> Laszlo
>
>
next prev parent reply other threads:[~2019-04-04 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 22:00 [Patch 0/4] Normalize line endings to CRLF in ARM packages Michael D Kinney
2019-04-03 22:00 ` [Patch 1/4] ArmPkg/ArmScmiDxe: Remove non-ASCII character in comment Michael D Kinney
2019-04-03 22:00 ` [Patch 2/4] ArmPkg: Normalize line endings to CRLF Michael D Kinney
2019-04-03 22:00 ` [Patch 3/4] ArmVirtPkg: " Michael D Kinney
2019-04-04 12:52 ` [edk2-devel] " Laszlo Ersek
2019-04-04 16:55 ` Michael D Kinney [this message]
2019-04-03 22:00 ` [Patch 4/4] ArmPlatformPkg: " Michael D Kinney
2019-04-04 3:54 ` [Patch 0/4] Normalize line endings to CRLF in ARM packages Leif Lindholm
2019-04-04 10:39 ` Laszlo Ersek
2019-04-04 17:00 ` Michael D Kinney
2019-04-04 17:17 ` [edk2-devel] " Kevin@Insyde
2019-04-05 3:24 ` Leif Lindholm
2019-04-05 18:11 ` Michael D Kinney
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=E92EE9817A31E24EB0585FDF735412F5B9C79264@ORSMSX112.amr.corp.intel.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