From: Greg KH <greg@kroah.com>
To: Juergen Gross <jgross@suse.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 00/13] Backport of patch series for stable 5.4 branch
Date: Tue, 3 Nov 2020 17:21:08 +0100 [thread overview]
Message-ID: <20201103162108.GA80864@kroah.com> (raw)
In-Reply-To: <20201103141321.20346-1-jgross@suse.com>
On Tue, Nov 03, 2020 at 03:13:08PM +0100, Juergen Gross wrote:
> V2: correct first patch
patch 1 updated
prev parent reply other threads:[~2020-11-03 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 14:13 [PATCH v2 00/13] Backport of patch series for stable 5.4 branch Juergen Gross
2020-11-03 14:13 ` [PATCH v2 01/13] xen/events: avoid removing an event channel while handling it Juergen Gross
2020-11-03 14:13 ` [PATCH v2 02/13] xen/events: add a proper barrier to 2-level uevent unmasking Juergen Gross
2020-11-03 14:13 ` [PATCH v2 03/13] xen/events: fix race in evtchn_fifo_unmask() Juergen Gross
2020-11-03 14:13 ` [PATCH v2 04/13] xen/events: add a new "late EOI" evtchn framework Juergen Gross
2020-11-03 14:13 ` [PATCH v2 05/13] xen/blkback: use lateeoi irq binding Juergen Gross
2020-11-03 14:13 ` [PATCH v2 06/13] xen/netback: " Juergen Gross
2020-11-03 14:13 ` [PATCH v2 07/13] xen/scsiback: " Juergen Gross
2020-11-03 14:13 ` [PATCH v2 08/13] xen/pvcallsback: " Juergen Gross
2020-11-03 14:13 ` [PATCH v2 09/13] xen/pciback: " Juergen Gross
2020-11-03 14:13 ` [PATCH v2 10/13] xen/events: switch user event channels to lateeoi model Juergen Gross
2020-11-03 14:13 ` [PATCH v2 11/13] xen/events: use a common cpu hotplug hook for event channels Juergen Gross
2020-11-03 14:13 ` [PATCH v2 12/13] xen/events: defer eoi in case of excessive number of events Juergen Gross
2020-11-03 14:13 ` [PATCH v2 13/13] xen/events: block rogue events for some time Juergen Gross
2020-11-03 16:21 ` 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=20201103162108.GA80864@kroah.com \
--to=greg@kroah.com \
--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 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.