Comment 6 for bug 1639924

Like found in 'doc/s390-upstream-prerequisites.md' as part of:
https://github.com/dynup/kpatch/pull/1203/commits/48d997f2a39c9151670b254570679b24d40abb7d
I checked the status of following kernel commits upstream and in jammy master-next:

**Prerequisite kernel patches:**
**v5.19:**
- 69505e3d9a39 bug: Use normal relative pointers in 'struct bug_entry'
==> upstream since v5.19-rc1, so not in jammy (but part of kinetic's target kernel 5.19)

**v5.18:**
- 602bf1687e6f s390/nospec: align and size extern thunks
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- 1d2ad084800e s390/nospec: add an option to use thunk-extern
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- eed38cd2f46f s390/nospec: generate single register thunks if possible
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- 2268169c14e5 s390: remove unused expoline to BC instructions
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- f0003a9e4c18 s390/entry: remove unused expoline thunk
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)

**v5.16:**
- torvalds/linux@f6ac18f sched: Improve try_invoke_on_locked_down_task()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@9b3c4ab sched,rcu: Rework try_invoke_on_locked_down_task()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@00619f7 sched,livepatch: Use task_call_func()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@8850cb6 sched: Simplify wake_up_*idle*()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@5de62ea sched,livepatch: Use wake_up_if_idle()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@96611c2 sched: Improve wake_up_all_idle_cpus() take #2
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)

**v5.15**
- torvalds/linux@de5012b s390/ftrace: implement hotpatching
==> upstream since v5.15, hence included in jammy (and kinetic)
- torvalds/linux@67ccddf ftrace: Introduce ftrace_need_init_nop()
==> upstream since v5.15, hence included in jammy (and kinetic)

**v5.14:**
- torvalds/linux@7561c14 s390/vdso: add .got.plt in vdso linker script
==> upstream since v5.14, hence included in jammy (and kinetic)

I've also found add. discussions and references about:
"livepatch: Kick idle cpu's tasks to perform transition"
and
"s390/nospec: build expoline.o for modules_prepare target"
"s390/nospec: remove unneeded header includes"
But one of them are upstream - are they required, too?