From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>
Subject: 回复: [edk2-devel] TianoCore Bug Triage - APAC / NAMO - Tue, 01/26/2021 6:30pm-7:30pm #cal-reminder
Date: Tue, 26 Jan 2021 12:36:05 +0800 [thread overview]
Message-ID: <012401d6f39c$c28433e0$478c9ba0$@byosoft.com.cn> (raw)
In-Reply-To: <UILz.1611628203384742994.Xv2f@groups.io>
[-- Attachment #1: Type: text/plain, Size: 2987 bytes --]
Hi all
Few new issues are reported. Let’s cancel the meeting this week.
<https://bugzilla.tianocore.org/show_bug.cgi?id=3186> 3186
EDK2
Code
unassigned@tianocore.org
UNCO
AllocSize = USBHC_MEM_ROUND (Size); // results in ASSERT when second last trb-address + 64 bytes croses end of 16 pages memblock in transfer ring with 0x1000 trb s each with 16 byte size <https://bugzilla.tianocore.org/show_bug.cgi?id=3186>
21:31:37
gopanho@gmail.com
<https://bugzilla.tianocore.org/show_bug.cgi?id=3187> 3187
EDK2
Code
unassigned@tianocore.org
UNCO
FaultTolerantWriteDxe defect will cause NVRAM not recovered after number of WorkSpaceRefresh(). <https://bugzilla.tianocore.org/show_bug.cgi?id=3187>
Sun 08:19
Marlboro.Chuang@dell.com
<https://bugzilla.tianocore.org/show_bug.cgi?id=3180> 3180
EDK2
Code
James.Bottomley@HansenPartn...
UNCO
OvmfPkg/PlatformBootManagerLibGrub: consider removing EfiBootManagerDispatchDeferredImages() call <https://bugzilla.tianocore.org/show_bug.cgi?id=3180>
Thu 13:41
lersek@redhat.com
<https://bugzilla.tianocore.org/show_bug.cgi?id=3179> 3179
EDK2
Code
ray.ni@intel.com
UNCO
MP: InterlockedIncrement ((UINT32 *) <https://bugzilla.tianocore.org/show_bug.cgi?id=3179> &CpuMpData->CpuCount) can be removed from ApWakeupFunction
Thu 04:43
ray.ni@intel.com
Thanks
Liming
发件人: bounce+27952+70752+4905953+8761045@groups.io <bounce+27952+70752+4905953+8761045@groups.io> 代表 devel@edk2.groups.io Calendar
发送时间: 2021年1月26日 10:30
收件人: devel@edk2.groups.io
主题: [edk2-devel] TianoCore Bug Triage - APAC / NAMO - Tue, 01/26/2021 6:30pm-7:30pm #cal-reminder
Reminder: TianoCore Bug Triage - APAC / NAMO
When: Tuesday, 26 January 2021, 6:30pm to 7:30pm, (GMT-08:00) America/Los Angeles
Where:https://meetingsamer34.webex.com/meetingsamer34/j.php?MTID=mb96c5bd411bd010e1e6d43a6f6c65f45
View Event <https://edk2.groups.io/g/devel/viewevent?eventid=1042698>
Organizer: Liming Gao gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn?subject=Re:%20Event:%20TianoCore%20Bug%20Triage%20-%20APAC%20%2F%20NAMO>
Description:
TianoCore Bug Triage - APAC / NAMO
Hosted by Liming Gao
https://meetingsamer34.webex.com/meetingsamer34/j.php?MTID=mb96c5bd411bd010e1e6d43a6f6c65f45
Wednesday, Jan 20, 2021 10:30 am | 50 minutes | (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Occurs every Wednesday effective 1/20/2021 from 10:30 AM to 11:20 AM, (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Meeting number: 126 867 1239
Password: ZhqYQunw246 (94797869 from video systems)
d8edc6c9604344b08f727b4bf054eaac_20210120T023000Z
Join by video system
Dial 1268671239@meetingsamer34.webex.com <mailto:1268671239@meetingsamer34.webex.com>
You can also dial 173.243.2.68 and enter your meeting number.
Join by phone
Use VoIP only
[-- Attachment #2: Type: text/html, Size: 14903 bytes --]
prev parent reply other threads:[~2021-01-26 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 2:30 TianoCore Bug Triage - APAC / NAMO - Tue, 01/26/2021 6:30pm-7:30pm #cal-reminder devel@edk2.groups.io Calendar
2021-01-26 4:36 ` gaoliming [this message]
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='012401d6f39c$c28433e0$478c9ba0$@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