On Thu, Jun 18 2026, Pranjal Shrivastava wrote: > On Mon, Jun 15, 2026 at 10:19:03PM +0000, David Matlack wrote: >> On 2026-06-12 10:47 AM, Pasha Tatashin wrote: >> > On 2026-06-12 09:54:44+03:00, Mike Rapoport wrote: >> > > On Fri, Jun 12, 2026 at 05:15:02AM +0000, Pasha Tatashin wrote: >> > > >> > > > On Fri, 22 May 2026 20:23:59 +0000, David Matlack >> > > > <[email protected]> wrote: >> > > > >> > > > Please add Pratyush, Mike, and myself so we are notified directly of >> > > > incoming patches, the same as with other areas where the liveupdate/ >> > > > tree is specified. >> > > >> > > Or we can add PCI liveupdate files to LIVEUPDATE entry. >> > >> > That will not work, as we cannot serve as maintainers for >> > PCI/VFIO/IOMMU/KVM, etc. David Matlack will be the maintainer for the >> > PCI components, and we will accept patches once they have been approved >> > by him. >> > >> > The simplification we could do is to create an email alias >> > for the live-update tree maintainers. This would allow us to use a >> > single entry instead of listing all three of us individually. >> >> We could create a Live Update mailing list for all code that can be CCed >> on all patches that must be merged through the Live Update tree. I would >> also be interested in subscribing to that list. > > +1. I'd like if there's a specific Live Update mailing list for > submissions & discussion about the Live Update tree.
We treat [email protected] as the "live update mailing list". We considered getting a separate one, but I reckon the traffic is low enough on kexec@ already that we can re-use it for live update. So perhaps we just Cc kexec@? Is there anything to be gained by creating an alias? -- Regards, Pratyush Yadav
