From: Henry Wang <xin.wang2@amd.com>
To: Oleksii K. <oleksii.kurochko@gmail.com>,
<xen-devel@lists.xenproject.org>
Cc: <committers@xenproject.org>, <kelly.choi@cloud.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Proposal to Extend Feature Freeze Deadline
Date: Wed, 15 May 2024 11:12:58 +0800 [thread overview]
Message-ID: <32f16048-c1ba-4ebb-a752-a77ed529a99c@amd.com> (raw)
In-Reply-To: <bba91b8b-b1cc-4054-96e8-80a63a3b808a@citrix.com>
Hi Oleksii,
On 5/14/2024 11:43 PM, Andrew Cooper wrote:
> On 14/05/2024 4:40 pm, Oleksii K. wrote:
>> Hello everyone,
>>
>> We're observing fewer merged patches/series across several
>> architectures for the current 4.19 release in comparison to previous
>> release.
>>
>> For example:
>> 1. For Arm, significant features like Cache Coloring and PCI
>> Passthrough won't be fully merged. Thus, it would be beneficial to
>> commit at least the following two patch series:
>> [1]https://lore.kernel.org/xen-devel/20240511005611.83125-1-xin.wang2@amd.com/
>>
>> [2]https://lore.kernel.org/xen-devel/20240424033449.168398-1-xin.wang2@amd.com/
>>
>> 2. For RISC-V, having the following patch series [3], mostly reviewed
>> with only one blocker [4], would be advantageous (As far as I know,
>> Andrew is planning to update his patch series):
>> [3]https://lore.kernel.org/xen-devel/cover.1713347222.git.oleksii.kurochko@gmail.com/
>> [4]
>> https://patchew.org/Xen/20240313172716.2325427-1-andrew.cooper3@citrix.com/
>>
>> 3. For PPC, it would be beneficial to have [5] merged:
>> [5]
>> https://lore.kernel.org/xen-devel/cover.1712893887.git.sanastasio@raptorengineering.com/
>>
>> Extending the feature freeze deadline by one week, until May 24th,
>> would provide additional time for merges mentioned above. This, in
>> turn, would create space for more features and fixes for x86 and other
>> common elements. If we agree to extend the feature freeze deadline,
>> please feel free to outline what you would like to see in the 4.19
>> release. This will make it easier to track our final goals and
>> determine if they are realistically achievable.
>>
>> I'd like to open the floor for discussion on this proposal. Does it
>> make sense, and would it be useful?
> Considering how many people are blocked on me, I'd welcome a little bit
> longer to get the outstanding series/fixes to land.
It would be great if we can extend the deadline for a week, thank you! I
will try my best to make progress of the two above-mentioned Arm series.
Kind regards,
Henry
next prev parent reply other threads:[~2024-05-15 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 15:40 Proposal to Extend Feature Freeze Deadline Oleksii K.
2024-05-14 15:43 ` Andrew Cooper
2024-05-15 3:12 ` Henry Wang [this message]
2024-05-15 13:27 ` Kelly Choi
2024-05-15 13:45 ` Oleksii K.
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-all 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=32f16048-c1ba-4ebb-a752-a77ed529a99c@amd.com \
--to=xin.wang2@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=kelly.choi@cloud.com \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).