All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <iwj@xenproject.org>
To: Julien Grall <julien@xen.org>
Cc: Jan Beulich <jbeulich@suse.com>,
	"xen-devel\@lists.xenproject.org"
	<xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
	Anthony Perard <anthony.perard@citrix.com>
Subject: Call for tools backports (was Re: preparations for 4.13.3)
Date: Wed, 17 Mar 2021 14:55:16 +0000	[thread overview]
Message-ID: <24658.6228.390535.850901@mariner.uk.xensource.com> (raw)
In-Reply-To: <b82a0932-761d-662c-baa4-59c4801ad5c8@xen.org>

Julien Grall writes ("Re: preparations for 4.13.3"):
> On 08/03/2021 09:49, Jan Beulich wrote:
> > All,
> > 
> > the release is overdue (my apologies). Please point out backports
> > you find missing from the respective staging branches, but which
> > you consider relevant.
> > > Ones that I have queued already, but which hadn't passed the push
> > gate to master yet when doing a swipe late last week, are
> > 
> > c6ad5a701b9a crypto: adjust rijndaelEncrypt() prototype for gcc11
> > 9318fdf757ec x86/shadow: suppress "fast fault path" optimization without reserved bits
> > 60c0444fae21 x86/shadow: suppress "fast fault path" optimization when running virtualized
> 
> I would like to also consider the following one:
> 
> 28804c0ce9fd SUPPORT.MD: Clarify the support state for the Arm SMMUv{1, 
> 2} drivers (4.11+ as updating the security support)
> 067935804a8e xen/vgic: Implement write to ISPENDR in vGICv{2, 3} (4.13+)
>      To support newer kernel on stable Xen
> d81133d45d81 xen/arm: Add workaround for Cortex-A53 erratum #843419 (4.13+)
> fd7479b9aec2 xen/arm: Add workaround for Cortex-A55 erratum #1530923 (4.13+)
> 5505f5f8e7e8 xen/arm: Add Cortex-A73 erratum 858921 workaround (4.13+)
> 63b4c9bfb788 xen/arm: mm: Access a PT entry before the table is unmapped 
> (4.13 only)
> f6790389613c xen/arm: sched: Ensure the vCPU context is seen before 
> vcpu_pause() returns (4.13 only)
> 
> I have put in parentheses the list of versions targeted.

My backport list seems to have very few tools patches on it.

If anyone has any tools bugfixes that ought to go into 4.13 please do
let me know!

Additionally, perhaps this one commit to be backported ?
  935e0836710ce8cab584155b2844cea8497a5159
  arm: replace typeof() with __typeof__()

Thanks,
Ian.


  reply	other threads:[~2021-03-17 14:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08  9:49 preparations for 4.13.3 Jan Beulich
2021-03-13 15:29 ` Julien Grall
2021-03-17 14:55   ` Ian Jackson [this message]
2021-03-19 10:26     ` Call for tools backports (was Re: preparations for 4.13.3) Julien Grall
2021-03-19 11:57     ` Andrew Cooper
2021-03-19 11:59       ` Jan Beulich
2021-03-19 13:21       ` Ian Jackson
2021-03-19 13:39         ` Andrew Cooper
2021-03-19 13:50           ` Ian Jackson
2021-03-19 13:48         ` Ian Jackson
2021-03-19 10:27   ` preparations for 4.13.3 Julien Grall
2021-03-19 19:40   ` Stefano Stabellini
2021-03-19 11:44 ` Andrew Cooper
2021-03-19 14:02   ` Jan Beulich
2021-03-19 18:43     ` Andrew Cooper

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=24658.6228.390535.850901@mariner.uk.xensource.com \
    --to=iwj@xenproject.org \
    --cc=anthony.perard@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --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.