public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Jiaxin" <jiaxin.wu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"Subramanian, Sriram" <sriram-s@hpe.com>,
	"Wang, Fan" <fan.wang@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ye, Ting" <ting.ye@intel.com>,
	"Fu, Siyuan" <siyuan.fu@intel.com>,
	"Subramanian@mx0b-002e3701.pphosted.com"
	<Subramanian@mx0b-002e3701.pphosted.com>
Subject: Re: [Patch v2] NetworkPkg: UefiPxeBcDxe: Add EXCLUSIVE attribute when opening SNP protocol installed by PXE.
Date: Wed, 19 Sep 2018 01:31:35 +0000	[thread overview]
Message-ID: <895558F6EA4E3B41AC93A00D163B727416494038@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <ec2b3259-94f6-c548-4087-47d6d81144d4@redhat.com>

> > Subject: [Patch v2] NetworkPkg: UefiPxeBcDxe: Add EXCLUSIVE attribute
> when opening SNP protocol installed by PXE.
> >
> > Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1152
> >
> > v2: Sync the same logic to Ipv6 and update code comments.
> >
> > The PXE driver installs a SNP and open this SNP with attribute BY_DRIVER
> > to avoid it being opened by MNP driver, this SNP is also expected not to
> > be opened by other drivers with EXCLUSIVE attribute. In some cases, other
> > drivers may happen to do this by error, and thus cause a system crash.
> > This patch adds EXCLUSIVE attribute when opening SNP in PXE driver, and
> > will reject all OpenProtocol requests by EXCLUSIVE.
> >
> > Cc: Subramanian, Sriram <sriram-s@hpe.com>
> > Cc: Ye Ting <ting.ye@intel.com>
> > Cc: Fu Siyuan <siyuan.fu@intel.com>
> > Cc: Wu Jiaxin <jiaxin.wu@intel.com>
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Wang Fan <fan.wang@intel.com>
> > ---
> >  NetworkPkg/UefiPxeBcDxe/PxeBcDriver.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> Either my edk2-devel subscription is breaking down, or our discipline
> regarding commit pushing is down the drain, recently.
> 
> This patch has been pushed as commit cde5a72d365e. Problems with that
> commit:
> 
> (1) The git authorship is marked as "edk2-devel-bounces@lists.01.org".
> That's *wrong*. This patch was authored by Wang Fan
> <fan.wang@intel.com>.
> 

Sorry Laszlo, I didn't check the "Author" field before pushing the patch as I received the commit request form Fan. I don't know whether it's the patch reason or TortoiseGit failed to fetch the "Signed-off-by" tag as "Author" field. Anyway, I will double check that. 

> (2) The commit lists Siyuan and Jiaxin as having given their reviews. I
> don't see their *v2* reviews anywhere on the list. I see their *v1*
> reviews, but the patch was changed in v2. Wang Fan was correct not to
> carry forward the v1 reviews into the v2 posting. If the v2 posting was
> fine, then Siyuan and Jiaxin should have confirmed that (with R-b's) on
> the list, before pushing the commit.
> 

Yes, you are right, Fan should include the v1 reviewer into the v2 posting, and the reviewer should confirm the new version patch even he/she is the final version committer.

> Another process failure that I'm witnessing is that people forget to
> close BZs once the corresponding fixes are upstream. Sorry but that just
> makes a joke out of bug tracking.
> 

Thanks the reminder, we will pay attention next time.

> Come on, guys. We can do better than this. Show some discipline and
> dedication to the process, please. The process is not self-serving; it's
> in place to promote mutual understanding.
> 
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-09-19  1:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  8:24 [Patch v2] NetworkPkg: UefiPxeBcDxe: Add EXCLUSIVE attribute when opening SNP protocol installed by PXE Wang Fan
2018-09-14  8:50 ` Subramanian, Sriram
2018-09-18 10:17   ` Laszlo Ersek
2018-09-19  1:31     ` Wu, Jiaxin [this message]
2018-09-19  1:44       ` Wu, Jiaxin
2018-09-19  1:46         ` Wang, Fan
2018-09-19 11:19       ` Laszlo Ersek

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=895558F6EA4E3B41AC93A00D163B727416494038@SHSMSX103.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