public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: "'Sami Mujawar'" <sami.mujawar@arm.com>,
	"'Laszlo Ersek'" <lersek@redhat.com>,
	"'Michael Kinney'" <michael.d.kinney@intel.com>,
	<devel@edk2.groups.io>, <ashishsingha@nvidia.com>,
	<quic_llindhol@quicinc.com>, <ardb+tianocore@kernel.org>,
	<jbrasen@nvidia.com>
Cc: <nd@arm.com>
Subject: 回复: edk2-stable202311: Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation
Date: Tue, 21 Nov 2023 09:04:44 +0800	[thread overview]
Message-ID: <02d401da1c16$b76c0960$26441c20$@byosoft.com.cn> (raw)
In-Reply-To: <b624601b-98c6-4296-9d9d-d4b1f1ed992b@arm.com>

Sami:
 I am OK to merge this patch for this stable bug. I will add push label for https://github.com/tianocore/edk2/pull/5061 

Thanks
Liming
> -----邮件原件-----
> 发件人: Sami Mujawar <sami.mujawar@arm.com>
> 发送时间: 2023年11月21日 0:07
> 收件人: Laszlo Ersek <lersek@redhat.com>; Liming Gao (Byosoft address)
> <gaoliming@byosoft.com.cn>; Michael Kinney <michael.d.kinney@intel.com>;
> devel@edk2.groups.io; ashishsingha@nvidia.com; quic_llindhol@quicinc.com;
> ardb+tianocore@kernel.org; jbrasen@nvidia.com
> 抄送: nd@arm.com
> 主题: edk2-stable202311: Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix
> ETE _UID Creation
> 
> Hi Laszlo, Liming, Mike,
> 
> Please see my response inline marked [SAMI].
> 
> Regards,
> 
> Sami Mujawar
> 
> On 17/11/2023 09:20 am, Laszlo Ersek wrote:
> > On 11/15/23 04:19, Ashish Singhal via groups.io wrote:
> >> Just like CPU _UID, ETE UID also needs to be unique so
> >> use AcpiProcessorUid instead of CpuName
> >>
> >> Signed-off-by: Ashish Singhal <ashishsingha@nvidia.com>
> >> ---
> >>   .../Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c | 5
> ++++-
> >>   1 file changed, 4 insertions(+), 1 deletion(-)
> > Is this a fixup for the recent feature
> >
> > [PATCH v3 00/11] Update MADT for ACPI 6.5, and add TRBE & ETE support
> > https://edk2.groups.io/g/devel/message/108996
> >
> > ?
> >
> > If so, then I *think* this qualifies to be merged during the hard
> > feature freeze (+Liming +Mike), but:
> 
> [SAMI] I raised a bugzilla for this issue at
> https://bugzilla.tianocore.org/show_bug.cgi?id=4600
> 
> and have also created a pull request at
> https://github.com/tianocore/edk2/pull/5061.
> 
> This patch has also passed the CI checks when I did a draft pull request.
> 
> I am not sure if I can apply the push label as we are in the code freeze
> stage.
> 
> Can you advise on how to proceed, please?
> 
> [/SAMI]
> 
> > - I think we should have a "Fixes:" tag in the commit message (for
> > pointing out the commit that should have contained the code being
> > added/updated now)
> >
> > - I think we should have a BZ too (also linked into the commit message).
> >
> > Laszlo
> >




-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111492): https://edk2.groups.io/g/devel/message/111492
Mute This Topic: https://groups.io/mt/102720225/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-11-21  1:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15  3:19 [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation Ashish Singhal via groups.io
2023-11-15 16:21 ` Leif Lindholm
2023-11-15 16:24   ` Ashish Singhal via groups.io
2023-11-15 17:20     ` Leif Lindholm
2023-11-15 17:27       ` Ashish Singhal via groups.io
2023-11-17  9:20 ` Laszlo Ersek
2023-11-17 16:37   ` Ashish Singhal via groups.io
2023-11-17 20:30     ` Laszlo Ersek
2023-11-17 22:14       ` Ashish Singhal via groups.io
2023-11-20 16:07   ` edk2-stable202311: " Sami Mujawar
2023-11-21  1:04     ` gaoliming via groups.io [this message]
2023-11-20 12:22 ` Sami Mujawar
2023-11-20 12:41   ` Sami Mujawar
  -- strict thread matches above, loose matches on Subject: below --
2023-11-21 11:56 回复: edk2-stable202311: " Sami Mujawar

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='02d401da1c16$b76c0960$26441c20$@byosoft.com.cn' \
    --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