From: Greg KH <gregkh@linuxfoundation.org>
To: Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: Juergen Gross <jgross@suse.com>,
Linux kernel regressions <regressions@lists.linux.dev>,
stable@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Xen developer discussion <xen-devel@lists.xenproject.org>
Subject: Re: gntdev warning fixes
Date: Sat, 9 Jul 2022 08:34:10 +0200 [thread overview]
Message-ID: <YskhYmJFg2KgYF3n@kroah.com> (raw)
In-Reply-To: <20220708163750.2005-1-demi@invisiblethingslab.com>
On Fri, Jul 08, 2022 at 12:37:44PM -0400, Demi Marie Obenour wrote:
> The recent gntdev fixes introduced two incorrect WARN_ON()s, which
> triggered immediately on my system. Patches for master and all
> supported stable versions follow.
>
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2022-07-09 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 16:37 gntdev warning fixes Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 4.19] Ignore failure to unmap -1 Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 4.14] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.4] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.10] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.15] Ignore failure to unmap INVALID_GRANT_HANDLE Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.18] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH master] " Demi Marie Obenour
2022-07-10 19:19 ` Oleksandr Tyshchenko
2022-07-09 6:34 ` Greg KH [this message]
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=YskhYmJFg2KgYF3n@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=demi@invisiblethingslab.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox