From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: wang.yi59@zte.com.cn, jiang.biao2@zte.com.cn, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] x86/kvm/vmx: Fix coding style in vmx_setup_l1d_flush()" was seriously submitted to be applied to the 4.18-stable tree?
Date: Mon, 10 Sep 2018 15:38:54 +0200 [thread overview]
Message-ID: <20180910133854.GD8309@kroah.com> (raw)
In-Reply-To: <80b4afcd-e110-11eb-279f-e5b35f1a5c40@redhat.com>
On Mon, Sep 10, 2018 at 01:08:26PM +0200, Paolo Bonzini wrote:
> On 01/09/2018 23:23, gregkh@linuxfoundation.org wrote:
> > The patch below was submitted to be applied to the 4.18-stable tree.
> >
> > I fail to see how this patch meets the stable kernel rules as found at
> > Documentation/process/stable-kernel-rules.rst.
> >
> > I could be totally wrong, and if so, please respond to
> > <stable@vger.kernel.org> and let me know why this patch should be
> > applied. Otherwise, it is now dropped from my patch queues, never to be
> > seen again.
>
> Since the L1TF patches are still seeing a little churn, I submitted all
> of them for stable, in order to avoid future conflicts.
I don't understand. Was this patch needed for something else? Or is it
already merged?
Totally confused,
greg k-h
next prev parent reply other threads:[~2018-09-10 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 21:23 WTF: patch "[PATCH] x86/kvm/vmx: Fix coding style in vmx_setup_l1d_flush()" was seriously submitted to be applied to the 4.18-stable tree? gregkh
2018-09-10 11:08 ` Paolo Bonzini
2018-09-10 13:38 ` Greg KH [this message]
2018-09-10 15:39 ` Paolo Bonzini
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=20180910133854.GD8309@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jiang.biao2@zte.com.cn \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wang.yi59@zte.com.cn \
/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.