From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: Michael Labriola <michael.d.labriola@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Sasha Levin <sashal@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Roger Pau Monne <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: Problems starting Xen domU after latest stable update
Date: Sun, 31 Jan 2021 00:25:13 +0100 [thread overview]
Message-ID: <20210130232513.GA6354@mail-itl> (raw)
In-Reply-To: <16a2f371-1c39-13f5-c214-e054b08abbab@suse.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Fri, Jan 29, 2021 at 03:16:52PM +0100, Jürgen Groß wrote:
> On 29.01.21 15:13, Michael Labriola wrote:
> > On Fri, Jan 29, 2021 at 12:26 AM Jürgen Groß <jgross@suse.com> wrote:
> > > If the buggy patch has been put into stable this Fixes: tag should
> > > result in the fix being put into the same stable branches as well.
> >
> > I've never done this before... does this happen automatically? Or is
> > there somebody we should ping to make sure it happens?
>
> This happens automatically (I think).
>
> I have seen mails for the patch been taken for 4.14, 4.19, 5.4 and 5.10.
Hmm, I can't find it in LKML archive, nor stable@ archive. And also it
isn't included in 5.10.12 released yesterday, nor included in
queue/5.10 [1]. Are you sure it wasn't lost somewhere in the meantime?
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=queue/5.10
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-30 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 23:52 Problems starting Xen domU after latest stable update Michael D Labriola
2021-01-28 23:52 ` Michael D Labriola
2021-01-29 0:03 ` Boris Ostrovsky
2021-01-29 0:39 ` Michael Labriola
2021-01-29 0:51 ` Marek Marczykowski-Górecki
2021-01-29 5:26 ` Jürgen Groß
2021-01-29 14:13 ` Michael Labriola
2021-01-29 14:16 ` Jürgen Groß
2021-01-30 23:25 ` Marek Marczykowski-Górecki [this message]
2021-01-31 17:22 ` Jason Andryuk
2021-01-29 15:19 ` [EXTERNAL] " David Woodhouse
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=20210130232513.GA6354@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dwmw@amazon.co.uk \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.d.labriola@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sashal@kernel.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.