From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jürgen Groß" <jgross@suse.com>
Cc: stable@vger.kernel.org
Subject: Re: Please add XSA fixes to stable branches 5.8 and 5.9
Date: Mon, 2 Nov 2020 13:24:00 +0100 [thread overview]
Message-ID: <20201102122400.GA666046@kroah.com> (raw)
In-Reply-To: <3c023ab7-5daf-da7b-4b3b-66c0c2e6a97c@suse.com>
On Mon, Nov 02, 2020 at 07:43:35AM +0100, Jürgen Groß wrote:
> Hi Greg,
>
> even while tagged with "Cc: stable@vger.kernel.org" you didn't take
> some upstream patches from 5.10-rc1 for the recent 5.8 and 5.9 stable
> branches:
Sorry, I am still 271 patches behind in those that were marked cc:
stable to be queued up yet. The influx of patches during the -rc1 merge
window that are cc: stable is, frankly, crazy. If these were so
important to be merged into 5.9.1, why didn't they get into 5.9.0?
Anyway, I'll work on these over the next few days, thanks...
greg k-h
next prev parent reply other threads:[~2020-11-02 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 6:43 Please add XSA fixes to stable branches 5.8 and 5.9 Jürgen Groß
2020-11-02 12:24 ` Greg Kroah-Hartman [this message]
2020-11-02 15:46 ` Greg Kroah-Hartman
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=20201102122400.GA666046@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).