[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Xen 4.18 release: Reminder about code freeze
On Tue, 26 Sep 2023, Henry Wang wrote: > Hi Jan, > > > On Sep 26, 2023, at 16:01, Jan Beulich <jbeulich@xxxxxxxx> wrote: > > > > On 26.09.2023 09:58, Henry Wang wrote: > >>> On Sep 26, 2023, at 15:46, Jan Beulich <jbeulich@xxxxxxxx> wrote: > >>> Furthermore may I ask that you keep an eye on the physical CPU hotplug > >>> situation? It continues to be documented as fully supported, and as long > >>> as > >>> that's the case 47342d8f490c (" x86/ACPI: Ignore entries with invalid > >>> APIC IDs > >>> when parsing MADT") would imo need reverting. While I had indicated that I > >>> would do the revert, a patch to SUPPORT.md was meanwhile proposed (which > >>> would of course further need accompanying by a CHANGELOG.md entry), but > >>> didn't > >>> really make progress since then. Yet I also didn't want to "needlessly" > >>> do the > >>> revert ... > >> > >> I think you are referring to [1] > > > > Yes, that's the one. > > > >> (and a proper CHANGELOG), I added this to my list > >> if all people involved is fine with this patch from Stefano, > > > > Iirc there were comments on the wording already, but no update to the patch. > > As this is simply a doc change, I think we still have time for the author > (Stefano) to respin > the patch. I am replying with his email address set to “To:” to catch his > attention. Also, > I think if Stefano is happy, probably any x86 maintainer or probably myself > can pick > this patch up as the follow up. It's out: https://marc.info/?l=xen-devel&m=169577443417860
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |