public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Dandan Bi <dandan.bi@intel.com>,  Eric Dong <eric.dong@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	 Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms] [patch v2 1/2] Platform/Intel: Add UserInterfaceFeaturePkg
Date: Mon, 17 Jun 2019 19:06:33 +0200	[thread overview]
Message-ID: <CAKv+Gu8TiX=SRwioFHHyvE4BG1vEZMnxSfUJQSNKX0efS9rH+w@mail.gmail.com> (raw)
In-Reply-To: <20190617164823.uxnoamz34ft24ak3@bivouac.eciton.net>

On Mon, 17 Jun 2019 at 18:48, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> Hi Dandan,
>
> On Mon, Jun 17, 2019 at 02:51:45PM +0800, Dandan Bi wrote:
> > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1545
> >
> > Add new package UserInterfaceFeaturePkg in Platform/Intel/
> > folder. It will keep UI related modules in this package.
> >
> > We plan add UserAuthentication modules in Platform/Intel.
> > Firstly we add a new package UserInterfaceFeaturePkg where
> > add the UserAuthentication modules into.
> > Package name follows the discussion in:
> > https://edk2.groups.io/g/devel/message/42286
> >
> > Cc: Eric Dong <eric.dong@intel.com>
> > Cc: Liming Gao <liming.gao@intel.com>
> > Signed-off-by: Dandan Bi <dandan.bi@intel.com>
> > ---
> >  Maintainers.txt                               |  4 ++++
> >  .../UserInterfaceFeaturePkg.dec               | 19 +++++++++++++++
> >  .../UserInterfaceFeaturePkg.dsc               | 23 +++++++++++++++++++
> >  3 files changed, 46 insertions(+)
> >  create mode 100644 Platform/Intel/UserInterfaceFeaturePkg/UserInterfaceFeaturePkg.dec
> >  create mode 100644 Platform/Intel/UserInterfaceFeaturePkg/UserInterfaceFeaturePkg.dsc
> >
> > diff --git a/Maintainers.txt b/Maintainers.txt
> > index cb9e15e880..c55a285fa1 100644
> > --- a/Maintainers.txt
> > +++ b/Maintainers.txt
> > @@ -71,10 +71,14 @@ R: Liming Gao <liming.gao@intel.com>
> >
> >  Platform/Intel/DebugFeaturePkg
> >  M: Eric Dong <eric.dong@intel.com>
> >  R: Liming Gao <liming.gao@intel.com>
> >
> > +Platform/Intel/UserInterfaceFeaturePkg
> > +M: Dandan Bi <dandan.bi@intel.com>
> > +R: Liming Gao <liming.gao@intel.com>
> > +
>
> Could you please cc all of the top-level maintainers (me, Ard and
> Mike) when modifying Maintainers.txt?
> Once the GetMaintainer.py we'll be able to do all of this more cleanly.
>
> I'm not saying you need all of our Reviewed-by:, but I'd like to not
> miss when new maintainerships are being added.
>

What is Intel specific about these user interface features? Do they
belong in Platform/Intel?

  reply	other threads:[~2019-06-17 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  6:51 [edk2-platforms] [patch v2 0/2] Add UserInterfaceFeaturePkg and UserAuthentication modules Dandan Bi
2019-06-17  6:51 ` [edk2-platforms] [patch v2 1/2] Platform/Intel: Add UserInterfaceFeaturePkg Dandan Bi
2019-06-17 16:48   ` [edk2-devel] " Leif Lindholm
2019-06-17 17:06     ` Ard Biesheuvel [this message]
2019-06-18  0:42       ` Liming Gao
2019-06-17  6:51 ` [edk2-platforms] [patch v2 2/2] Platform/Intel/UserInterfaceFeaturePkg: Add UserAuthentication modules Dandan Bi

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='CAKv+Gu8TiX=SRwioFHHyvE4BG1vEZMnxSfUJQSNKX0efS9rH+w@mail.gmail.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