All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii <oleksii.kurochko@gmail.com>
To: "Jan Beulich" <jbeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Cc: committers@xenproject.org, community.manager@xenproject.org,
	Kelly Choi <kelly.choi@cloud.com>,
	xen-devel@lists.xenproject.org
Subject: Re: Xen 4.19 release status tracking list [ May ]
Date: Mon, 06 May 2024 10:25:40 +0200	[thread overview]
Message-ID: <609d3d5da1c95b14281233860f7619e6d15de195.camel@gmail.com> (raw)
In-Reply-To: <8c0bc745-05f5-4839-b920-7830e2c55688@suse.com>

On Mon, 2024-05-06 at 09:11 +0200, Jan Beulich wrote:
> On 03.05.2024 18:54, Oleksii wrote:
> > *** x86 ***:
> >   * [PATCH 0/4] iommu/x86: fixes/improvements for unity range
> > checks [
> > https://lore.kernel.org/xen-devel/20240201170159.66330-1-roger.pau@citrix.com/
> > ]:
> >     - almost patch series have been merged already except the
> > patch:
> >         [PATCH 4/4] iommu/x86: make unity range checking more
> > strict
> > 
> >   * [PATCH 0/8] x86: support AVX10.1 [
> > https://lore.kernel.org/xen-devel/298db76f-d0ee-4d47-931f-1baa1a7546cf@suse.com/
> > ]:
> >     - two patches of patch series are waitng to merged/reviewed:
> >       [PATCH 1/4] amd-vi: fix IVMD memory type checks
> >       [PATCH 4/4] iommu/x86: make unity range checking more strict 
> 
> This sub-item doesn't really fit the topic, and seems to rather
> belong
> to the earlier one? 
Thanks for correction, it is belonged to previous topic.

> Where (correctly) 1/4 isn't listed anymore, for
> having gone in. As to 4/4 - Roger, I'm not sure I can conclude what
> the
> plan here was: Are you meaning to submit an updated version, or did
> we
> rather settle on not further pursuing this?
> 
> >   * APX support?
> 
> I think you should drop this now. I'm throttling further work on the
> insn
> emulator, as long as I have so many other patches there pending
> review.
> 
> >   * [PATCH v6 0/4] x86/pvh: Support relocating dom0 kernel [
> > https://patchew.org/Xen/20240327215102.136001-1-jason.andryuk@amd.com/
> > ]
> 
> There had been a v7, and all of that plus a follow-on adjustment have
> gone
> in.
> 
> > *** common ***:
> >   * annotate entry points with type and size" series:
> >     The bulk of this has gone in, but there'll want to be follow-
> > ups.
> 
> I think these follow-ups now want tracking on a per-arch basis (x86
> and
> Arm, with PPC and RISC-V filly done).
> 
> >   * [PATCH v2 (resend) 00/27] Remove the directmap [
> > https://lore.kernel.org/xen-devel/20240116192611.41112-1-eliasely@amazon.com/
> > ]
> >     - 7/27 were merged.
> 
> Hmm, no, I don't think that one was. Other were, yes.
> 
> >   * [PATCH v6 0/7] MSI-X support with qemu in stubdomain, and other
> > related changes:
> >     - new patch version was sent
> 
> 1/7 was committed.
> 
> >   * [PATCH v3 0/4] xenwatchdogd bugfixes and enhancements [
> > https://lore.kernel.org/xen-devel/20240411182023.56309-1-leigh@solinno.co.uk/
> > ]:
> >     new patch series were sent.
> 
> Was there anything left from that series?
I double-checked and everything has been merged. Thanks for correction.

I'm considering writing a script to automate the process of checking
whether the patches in a patch series have been merged or not.
Currently, I'm doing it manually, so there's a chance I might miss
something. It would be helpful if such a script already exists.

~ Oleksii


  reply	other threads:[~2024-05-06  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 16:54 Xen 4.19 release status tracking list [ May ] Oleksii
2024-05-06  7:11 ` Jan Beulich
2024-05-06  8:25   ` Oleksii [this message]
2024-05-06  9:26 ` Roger Pau Monné
2024-05-06  9:35   ` Jan Beulich
2024-05-06 10:34     ` Roger Pau Monné

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=609d3d5da1c95b14281233860f7619e6d15de195.camel@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=committers@xenproject.org \
    --cc=community.manager@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=kelly.choi@cloud.com \
    --cc=roger.pau@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.