From: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-scsi@vger.kernel.org,
Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
stable@vger.kernel.org
Subject: RE: [PATCH] mpt3sas: Use driver scsi lookup to track outstanding IOs
Date: Tue, 19 Feb 2019 19:14:17 +0530 [thread overview]
Message-ID: <159855771db2192a00c3c248f0e3cab9@mail.gmail.com> (raw)
In-Reply-To: <20190219121415.GA23831@kroah.com>
Greg,
This patch will fix the issue discussed in below email thread,
https://patchwork.kernel.org/patch/10734933/
Yesterday same issue is been reported by Michal Soltys in below thread,
https://marc.info/?l=linux-scsi&m=155057830803859&w=2
Thanks,
Sreekanth
-----Original Message-----
From: Greg KH [mailto:gregkh@linuxfoundation.org]
Sent: Tuesday, February 19, 2019 5:44 PM
To: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Cc: linux-scsi@vger.kernel.org; Sathya.Prakash@broadcom.com;
suganath-prabu.subramani@broadcom.com; stable@vger.kernel.org
Subject: Re: [PATCH] mpt3sas: Use driver scsi lookup to track outstanding
IOs
On Tue, Feb 19, 2019 at 07:02:46AM -0500, Sreekanth Reddy wrote:
> Use driver's scsiio lookup table to track outstanding IOs at driver
> level,
And why is this a stable kernel patch?
You do not have a "Fixes:" tag in here. It really looks like a new
feature :(
greg k-h
next prev parent reply other threads:[~2019-02-19 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 12:02 [PATCH] mpt3sas: Use driver scsi lookup to track outstanding IOs Sreekanth Reddy
2019-02-19 12:14 ` Greg KH
2019-02-19 13:44 ` Sreekanth Reddy [this message]
2019-02-21 4:07 ` Sasha Levin
2019-02-25 17:25 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2019-02-19 12:00 Sreekanth Reddy
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=159855771db2192a00c3c248f0e3cab9@mail.gmail.com \
--to=sreekanth.reddy@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sathya.prakash@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=suganath-prabu.subramani@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox