preparations for 4.14.5 ?

[Jan Beulich <jbeulich@suse.com>]

All,

while 4.14's general support period ended in January, we're considering
to cut an out-of-band release due to the relatively large number of
security relevant backports which has accumulated in just 2 months. By
doing this we would _not_ be promising to do so again in the future.
Please voice objections to the plan (or support for it) in the next
couple of days.

Since it's a little easier to "batch" releases, I would intend to keep
4.14.5 aligned with 4.16.1.

Commits I have queued but not committed to the branch yet (and I won't
until in a couple of days time, to allow for objections to the plan to
be raised):

dd6c062a7a4a tools/libxl: Correctly align the ACPI tables
aa390d513a67 build: fix exported variable name CFLAGS_stack_boundary
e62cc29f9b6c tools/libs: Fix build dependencies
eddf13b5e940 x86emul: fix VPBLENDMW with mask and memory operand
6bd1b4d35c05 x86/console: process softirqs between warning prints
07449ecfa425 tools/libxl: don't allow IOMMU usage with PoD
10454f381f91 xz: avoid overlapping memcpy() with invalid input with in-place decompression
0a21660515c2 xz: validate the value before assigning it to an enum variable
b4f211606011 vpci/msix: fix PBA accesses

Please point out backports you find missing from both the respective
staging branch and the list above, but which you consider relevant.

Jan