From: Greg KH <gregkh@linuxfoundation.org>
To: Pradeep Sawlani <sawlani@google.com>
Cc: stable@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH] KVM: Fix stack-out-of-bounds read in write_mmio
Date: Tue, 9 Jan 2018 15:44:04 +0100 [thread overview]
Message-ID: <20180109144404.GA13228@kroah.com> (raw)
In-Reply-To: <CAKvfMH+JNnfiTzxqz8-DFevkYkphwujUL0nyigGyjqpHUwxm0A@mail.gmail.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Tue, Jan 09, 2018 at 06:28:29AM -0800, Pradeep Sawlani wrote:
> 4.4.110 stable tree.
What about 4.9 and 4.14? You do not want to cause a regression if
someone moves from 4.4.y to 4.9.y, right?
> bwh was internal thing which got here. Do you want me to modify commit
> message and send it across?
It makes no sense in the context, the person who did the work should
sign-off on the patch, right?
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-09 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 14:15 [PATCH] KVM: Fix stack-out-of-bounds read in write_mmio sawlani
2018-01-09 14:25 ` Greg KH
[not found] ` <CAKvfMH+JNnfiTzxqz8-DFevkYkphwujUL0nyigGyjqpHUwxm0A@mail.gmail.com>
2018-01-09 14:44 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 15:24 sawlani
2018-01-10 12:14 ` Greg KH
2018-01-10 13:06 ` Paolo Bonzini
2018-01-10 15:04 ` Greg KH
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=20180109144404.GA13228@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christoffer.dall@linaro.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sawlani@google.com \
--cc=stable@vger.kernel.org \
--cc=wanpeng.li@hotmail.com \
/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.