From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "xen/events/fifo: Handle linked events when closing a port" has been added to the 4.1-stable tree
Date: Fri, 14 Aug 2015 10:26:01 -0700 [thread overview]
Message-ID: <20150814172601.GC17745@kroah.com> (raw)
In-Reply-To: <835394C5C88961479E6675195CC945E0451E21@AMSPEX01CL03.citrite.net>
On Fri, Aug 14, 2015 at 08:13:26AM +0000, David Vrabel wrote:
> The commit causes WARNING spam and has been reverted. Please don't backport.
Thanks for letting me know, now removed.
greg k-h
prev parent reply other threads:[~2015-08-14 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 0:44 Patch "xen/events/fifo: Handle linked events when closing a port" has been added to the 4.1-stable tree gregkh
2015-08-14 8:13 ` David Vrabel
2015-08-14 17:26 ` gregkh [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=20150814172601.GC17745@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=david.vrabel@citrix.com \
--cc=ross.lagerwall@citrix.com \
--cc=stable-commits@vger.kernel.org \
--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).