From: Greg KH <gregkh@linuxfoundation.org>
To: Amos Kong <akong@redhat.com>
Cc: stable@vger.kernel.org, rusty@rustcorp.com.au,
amit.shah@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [3.16 stable PATCH 0/2] virtio-rng: two backports to fix stuck
Date: Tue, 18 Nov 2014 17:20:22 -0800 [thread overview]
Message-ID: <20141119012022.GB22731@kroah.com> (raw)
In-Reply-To: <20141104043227.GA13409@air.redhat.com>
On Tue, Nov 04, 2014 at 12:32:27PM +0800, Amos Kong wrote:
> On Sat, Oct 11, 2014 at 06:51:47AM +0800, Amos Kong wrote:
> > I received two mails about faile to apply patches to 3.16-stable tree:
> >
> > FAILED: patch "[PATCH] virtio-rng: skip reading when we start to remove the device" failed to apply to 3.16-stable tree
> > FAILED: patch "[PATCH] virtio-rng: fix stuck of hot-unplugging busy device" failed to apply to 3.16-stable tree
> >
> > Amit already backported two patches for 3.16-stable, then cherry-pick
> > of my two patches works.
> >
> > Thanks.
>
> Ping Greg, thanks.
Why me? 3.16-stable is end-of-life, I'm no longer maintaining it, so
what can I do here with these patches?
confused,
greg k-h
prev parent reply other threads:[~2014-11-19 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 22:51 [3.16 stable PATCH 0/2] virtio-rng: two backports to fix stuck Amos Kong
2014-10-10 22:51 ` [3.16 stable PATCH 1/2] virtio-rng: fix stuck of hot-unplugging busy device Amos Kong
2014-10-10 22:51 ` [3.16 stable PATCH 2/2] virtio-rng: skip reading when we start to remove the device Amos Kong
2014-11-04 4:32 ` [3.16 stable PATCH 0/2] virtio-rng: two backports to fix stuck Amos Kong
2014-11-05 16:02 ` Luis Henriques
2014-11-05 16:14 ` Amos Kong
2014-11-19 1:20 ` 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=20141119012022.GB22731@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akong@redhat.com \
--cc=amit.shah@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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