public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <sami.mujawar@arm.com>,
	"'Laszlo Ersek'" <lersek@redhat.com>,
	"'Michael Kinney'" <michael.d.kinney@intel.com>,
	<ashishsingha@nvidia.com>, <quic_llindhol@quicinc.com>,
	<ardb+tianocore@kernel.org>, "'Jeff Brasen'" <jbrasen@nvidia.com>
Cc: "'nd'" <nd@arm.com>
Subject: 回复: 回复: edk2-stable202311: Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation
Date: Tue, 21 Nov 2023 22:14:31 +0800	[thread overview]
Message-ID: <03f101da1c85$0be276f0$23a764d0$@byosoft.com.cn> (raw)
In-Reply-To: <61F7F1EE-02C3-4DF9-AD8D-0006829FB99E@arm.com>

Sami:
  I have merged it. Please check. 

Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Sami
> Mujawar
> 发送时间: 2023年11月21日 19:57
> 收件人: gaoliming <gaoliming@byosoft.com.cn>; '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; Jeff Brasen (jbrasen@nvidia.com)
> <jbrasen@nvidia.com>
> 抄送: nd <nd@arm.com>
> 主题: Re: 回复: edk2-stable202311: Re: [edk2-devel] [PATCH]
> DynamicTablesPkg: Fix ETE _UID Creation
> 
> Hi Liming,
> 
> On 21/11/2023, 01:05, "gaoliming" <gaoliming@byosoft.com.cn
> <mailto:gaoliming@byosoft.com.cn>> wrote:
> 
> 
> 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
> <https://github.com/tianocore/edk2/pull/5061>
> [SAMI] Thank you for picking this patch for the stable tag. Apparently, the
> patch does not seem to have merged.
> I am not sure if you have already applied the push label. Please let me know if
> there are any issues that I can help with.
> 
> Regards,
> 
> Sami Mujawar
> 
> Thanks
> Liming
> > -----邮件原件-----
> > 发件人: Sami Mujawar <sami.mujawar@arm.com
> <mailto:sami.mujawar@arm.com>>
> > 发送时间: 2023年11月21日 0:07
> > 收件人: Laszlo Ersek <lersek@redhat.com <mailto:lersek@redhat.com>>;
> Liming Gao (Byosoft address)
> > <gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn>>; Michael
> Kinney <michael.d.kinney@intel.com <mailto:michael.d.kinney@intel.com>>;
> > devel@edk2.groups.io <mailto:devel@edk2.groups.io>;
> ashishsingha@nvidia.com <mailto:ashishsingha@nvidia.com>;
> quic_llindhol@quicinc.com <mailto:quic_llindhol@quicinc.com>;
> > ardb+tianocore@kernel.org <mailto:ardb+tianocore@kernel.org>;
> jbrasen@nvidia.com <mailto:jbrasen@nvidia.com>
> > 抄送: nd@arm.com <mailto: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
> <mailto: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
> <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
> <https://bugzilla.tianocore.org/show_bug.cgi?id=4600>
> >
> > and have also created a pull request at
> > https://github.com/tianocore/edk2/pull/5061
> <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 (#111547): https://edk2.groups.io/g/devel/message/111547
Mute This Topic: https://groups.io/mt/102728858/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 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 11:56 回复: edk2-stable202311: Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation Sami Mujawar
2023-11-21 14:14 ` gaoliming via groups.io [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-21 14:16 回复: " 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='03f101da1c85$0be276f0$23a764d0$@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