public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Boaz Kahana <Boaz_Kahana@Phoenix.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Protocol EFI_FORM_BROWSER_EXTENSION_PROTOCOL - included in UDK code but not part of the spec
Date: Wed, 21 Sep 2016 03:56:53 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B47B0B2@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <60b0bbecb9a64ffc9dfb1f1947c9b75f@SCL-EXCHMB-13.phoenix.com>

Boaz:
  This protocol is edk2 implement protocol. We have no plan to propose it to UEFI spec. Its EFI_ prefix is history reason. To avoid the incompatible change, we don't change its definition. But for any new introduced protocol, we will insist on this rule without EFI_ prefix. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Boaz Kahana
> Sent: Friday, September 16, 2016 8:25 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Protocol EFI_FORM_BROWSER_EXTENSION_PROTOCOL -
> included in UDK code but not part of the spec
> 
> The protocol EFI_FORM_BROWSER_EXTENSION_PROTOCOL is defined in
> MdeModulePkg\Include\Protocol\FormBrowserEx.h with EFI_ prefix
> although it is not part of the UEFI spec.
> (It was added by Intel - Liming - in Sep 2011)
> 
> IMHO it should be added to the UEFI spec otherwise it should not use the
> EFI_ prefix.
> 
> Boaz
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2016-09-21  3:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16  0:24 Protocol EFI_FORM_BROWSER_EXTENSION_PROTOCOL - included in UDK code but not part of the spec Boaz Kahana
2016-09-21  3:56 ` Gao, Liming [this message]
2016-09-21 16:03   ` Tim Lewis
2016-09-21 16:26     ` Kinney, Michael D
2016-09-22  2:08       ` Gao, Liming

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=4A89E2EF3DFEDB4C8BFDE51014F606A14B47B0B2@shsmsx102.ccr.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