On Thu, Nov 10, 2022 at 06:32:54PM -0300, Guilherme G. Piccoli wrote: > [Trimming long CC list] > > Hi Wei / Michael, just out of curiosity, did this (and patch 9) ended-up > being queued in hyperv-next? > No. They are not queued. I didn't notice Michael's email and thought they would be picked up by someone else while dealing with the whole series. I will pick them up later. Thanks, Wei. > Thanks in advance, > > > Guilherme > > On 17/10/2022 12:26, Michael Kelley (LINUX) wrote: > > From: Guilherme G. Piccoli <gpiccoli@xxxxxxxxxx> Sent: Tuesday, October 4, 2022 10:20 AM > >> > >> On 04/10/2022 13:24, Michael Kelley (LINUX) wrote: > >>> [...] > >>> > >>> Tested this patch in combination with Patch 9 in this series. Verified > >>> that both the panic and die paths work correctly with notification to > >>> Hyper-V via hyperv_report_panic() or via hv_kmsg_dump(). Hyper-V > >>> framebuffer is updated as expected, though I did not reproduce > >>> a case where the ring buffer lock is held. vmbus_initiate_unload() runs > >>> as expected. > >>> > >>> Tested-by: Michael Kelley <mikelley@xxxxxxxxxxxxx> > >>> > >> > >> Thanks a lot for the tests/review Michael! > >> > >> Do you think Hyper-V folks could add both patches in hv tree? If you > >> prefer, I can re-send them individually. > >> > > > > Wei Liu: Could you pick up Patch 9 and Patch 10 from this series in the > > hyperv-next tree? > > > > Michael > > _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
