From: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>,
Chaitra Basappa <chaitra.basappa@broadcom.com>,
linux-scsi@vger.kernel.org
Cc: Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>,
stable@vger.kernel.org
Subject: RE: [PATCH v1 14/15] mpt3sas: fix possible memory leak.
Date: Tue, 10 Apr 2018 22:20:04 +0530 [thread overview]
Message-ID: <5f03809eea5b524a1e656334f397e4e4@mail.gmail.com> (raw)
In-Reply-To: <DM5PR2101MB1032E7EF8D8EEBAC0BD6DEEFFBBE0@DM5PR2101MB1032.namprd21.prod.outlook.com>
Yes Sasha, We like to have this patch included in a stable tree.
Thanks,
Sreekanth
-----Original Message-----
From: Sasha Levin [mailto:Alexander.Levin@microsoft.com]
Sent: Tuesday, April 10, 2018 7:19 PM
To: Sasha Levin; Chaitra P B; linux-scsi@vger.kernel.org
Cc: Sathya.Prakash@broadcom.com; sreekanth.reddy@broadcom.com;
stable@vger.kernel.org
Subject: Re: [PATCH v1 14/15] mpt3sas: fix possible memory leak.
Hi,
[This is an automated email]
This commit has been processed by the -stable helper bot and determined to
be a high probability candidate for -stable trees. (score: 12.9808)
The bot has tested the following trees: v4.16.1, v4.15.16, v4.14.33,
v4.9.93, v4.4.127.
v4.16.1: Build OK!
v4.15.16: Build OK!
v4.14.33: Build OK!
v4.9.93: Build OK!
v4.4.127: Build OK!
Please let us know if you'd like to have this patch included in a stable
tree.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-04-10 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1522943197-5408-15-git-send-email-chaitra.basappa@broadcom.com>
2018-04-10 13:49 ` [PATCH v1 14/15] mpt3sas: fix possible memory leak Sasha Levin
2018-04-10 13:49 ` Sasha Levin
2018-04-10 16:50 ` Sreekanth Reddy [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=5f03809eea5b524a1e656334f397e4e4@mail.gmail.com \
--to=sreekanth.reddy@broadcom.com \
--cc=Alexander.Levin@microsoft.com \
--cc=chaitra.basappa@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sathya.prakash@broadcom.com \
--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 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.