Re: [PATCH 2/3] tools/libxc: change xc_memshr_fork_reset API to match hypervisor

[Tamas K Lengyel <tamas.k.lengyel@xxxxxxxxx>]

On Wed, May 18, 2022 at 11:48 AM Jan Beulich <jbeulich@xxxxxxxx> wrote:
>
> On 18.05.2022 17:01, Tamas K Lengyel wrote:
> > On Thu, May 12, 2022 at 9:46 AM Tamas K Lengyel
> > <tamas.k.lengyel@xxxxxxxxx> wrote:
> >>
> >> On Thu, May 5, 2022 at 4:27 AM Roger Pau Monné <roger.pau@xxxxxxxxxx> 
> >> wrote:
> >>>
> >>> On Wed, Apr 27, 2022 at 11:34:19AM -0400, Tamas K Lengyel wrote:
> >>>> Need to separately specify if the reset is for the memory or for the VM 
> >>>> state,
> >>>> or both.
> >>>>
> >>>> Signed-off-by: Tamas K Lengyel <tamas.lengyel@xxxxxxxxx>
> >>>
> >>> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
> >>
> >> Patch ping. Can this patch be merged please?
> >
> > Patch ping.
>
> Your mail (and I guess also your earlier one) was _To_ Roger, which
> is odd since he already did provide R-b. What you're missing is a
> tool stack maintainer ack aiui, so it may help if you send your
> pings _To_ the respective people.

True, but all the toolstack maintainers have been CC-d from the start.
Is it the case that CC-ing is now officially insufficient? What's the
point of ./scripts/add_maintainers.pl then which specifically adds
maintainers only as CC? How are you supposed to get their attention?
Just know you specifically have to send emails to them and not the
mailinglist? I'm getting the distinct impression that the toolstack
side has simply become unmaintained/orphaned with no one left who
actually is looking at the mailinglist.

Tamas