public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel@lists.01.org, lersek@redhat.com
Subject: Re: [PATCH] ArmPlatformPkg ArmVirtPkg: reorganize PL011 code
Date: Thu, 16 Nov 2017 17:36:20 +0000	[thread overview]
Message-ID: <20171116173620.yovvab2cuqiqyr5l@bivouac.eciton.net> (raw)
In-Reply-To: <20171116171216.7566-1-ard.biesheuvel@linaro.org>

On Thu, Nov 16, 2017 at 05:12:16PM +0000, Ard Biesheuvel wrote:
> The PL011 code in ArmPlatformPkg is organized in a weird way: there is
> a single PL011Uart.h header file under Include/Drivers containing both
> register definitions and function entry points. The PL011Uart library
> itself is in Drivers/ but it is actually a library.
> 
> So let's clean this up: add a new PL011UartLib library class and associated
> header file containing only the library prototypes, and move the library
> itself under Library/ using a new GUID, with the register definitions moved
> into a local header file.
> 
> Note that we need to retain the old implementation for out of tree
> platforms,

s/need to//

Do we need to?
I mean, we could, and give a bit of a warning for people to switch
over. But does the change actually entail anything more than pointing
to the new .inf location? If not, we're just moving the point at
which platforms fail and have to modify their .dsc/.fdf.

That said, I'm not religiously opposed to a grace period - but I
don't want the old version hanging around to get included in the next
UDK release.

I _would_ prefer to see the ArmVirtPkg change as a separate patch.
Especially if the old copy is kept around.

Nice bit of cleanup though.

/
    Leif


  reply	other threads:[~2017-11-16 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 17:12 [PATCH] ArmPlatformPkg ArmVirtPkg: reorganize PL011 code Ard Biesheuvel
2017-11-16 17:36 ` Leif Lindholm [this message]
2017-11-16 17:38   ` Ard Biesheuvel
2017-11-16 18:12     ` Leif Lindholm

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=20171116173620.yovvab2cuqiqyr5l@bivouac.eciton.net \
    --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