All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Marek Marczykowski <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Backports to stable
Date: Mon, 08 Oct 2018 03:29:06 -0600	[thread overview]
Message-ID: <5BBB236202000078001EF6EC@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20181007010433.GB2975@mail-itl>

>>> On 07.10.18 at 03:04, <marmarek@invisiblethingslab.com> wrote:
> I'd like to propose backporting GCC7/8 fixes to all stable branches. Below
> is a list up to stable-4.6, but some of the patches are already on
> select branches (developed during that release cycle, or already
> backported).

I continue to be opposed to backporting anything that is not needed
for dealing security issues to branches which are in security-support-
only mode, i.e. anything older than 4.8 at this point in time.

Furthermore I notice that 4.6 has just moved out of security support,
at the end of last week.

>     e0a97098e2 x86: fix section type mismatch in mm.c

This describes itself as a Clang fix - has it become relevant for
gcc now too? Anyway - this has been in even the original 4.7.0,
so as per above not a candidate for any actively maintained
branch.

>     # This one doesn't apply cleanly, because acpi stuff moved
>     # tools/firmware/hvmloader/acpi -> tools/acpi
>     858dbaaeda libacpi: fixes for iasl >= 20180427

Iirc I've applied this back to 4.8 already, and quite some time ago.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-10-08  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07  1:04 Backports to stable Marek Marczykowski-Górecki
2018-10-08  9:29 ` Jan Beulich [this message]
2018-10-08 10:40   ` Marek Marczykowski
2018-10-08 11:57     ` Jan Beulich

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=5BBB236202000078001EF6EC@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=marmarek@invisiblethingslab.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.