From: Sasha Levin <sashal@kernel.org>
To: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
linux-efi@vger.kernel.org,
Rob Bradford <robert.bradford@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Gen Zhang <blackgod016574@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
akaher@vmware.com, srinidhir@vmware.com, bvikas@vmware.com,
amakhalov@vmware.com, srivatsab@vmware.com,
netdev@vger.kernel.org
Subject: Re: [4.19.y PATCH 0/3] Backported fixes for 4.19 stable tree
Date: Fri, 28 Jun 2019 16:44:42 -0400 [thread overview]
Message-ID: <20190628204442.GI11506@sasha-vm> (raw)
In-Reply-To: <156174726746.34985.1890238158382638220.stgit@srivatsa-ubuntu>
On Fri, Jun 28, 2019 at 11:41:54AM -0700, Srivatsa S. Bhat wrote:
>Hi Greg,
>
>This patchset includes a few backported fixes for the 4.19 stable tree.
>I would appreciate if you could kindly consider including them in the
>next release.
+ netdev@
David Miller deals with the 4.19 net/ patches, so this will need to go
through (or acked by) him.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-06-28 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 18:41 [4.19.y PATCH 0/3] Backported fixes for 4.19 stable tree Srivatsa S. Bhat
2019-06-28 18:42 ` [4.19.y PATCH 1/3] efi/x86/Add missing error handling to old_memmap 1:1 mapping code Srivatsa S. Bhat
2019-06-29 6:57 ` Greg KH
2019-06-29 8:47 ` Ard Biesheuvel
2019-06-29 8:57 ` Gen Zhang
2019-06-29 9:10 ` Greg KH
2019-06-29 21:11 ` Ard Biesheuvel
2019-06-29 21:49 ` Srivatsa S. Bhat
2019-06-28 20:44 ` Sasha Levin [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=20190628204442.GI11506@sasha-vm \
--to=sashal@kernel.org \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=ard.biesheuvel@linaro.org \
--cc=blackgod016574@gmail.com \
--cc=bvikas@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-efi@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=robert.bradford@intel.com \
--cc=srinidhir@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@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