From: Greg KH <gregkh@linuxfoundation.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: cdall@linaro.org, stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses" has been added to the 4.4-stable tree
Date: Wed, 17 May 2017 10:33:22 +0200 [thread overview]
Message-ID: <20170517083322.GB26474@kroah.com> (raw)
In-Reply-To: <86bmqs7yva.fsf@arm.com>
On Wed, May 17, 2017 at 07:59:05AM +0100, Marc Zyngier wrote:
> Hi Greg,
>
> On Tue, May 16 2017 at 11:53:26 AM, <gregkh@linuxfoundation.org> wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
> >
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > arm64-kvm-fix-decoding-of-rt-rt2-when-trapping-aarch32-cp-accesses.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Please drop this patch from 4.4, it doesn't compile (missing crucial
> dependencies, reported by the kbuild robot). I'll provide an updated
> patch early next week (unless someone beats me to it -- I'm traveling
> ATM).
Ok, now dropped, thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2017-05-17 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 10:53 Patch "arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses" has been added to the 4.4-stable tree gregkh
2017-05-17 6:59 ` Marc Zyngier
2017-05-17 8:33 ` Greg KH [this message]
2017-05-18 7:07 ` Marc Zyngier
2017-05-18 7:20 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 7:20 gregkh
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=20170517083322.GB26474@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cdall@linaro.org \
--cc=marc.zyngier@arm.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).