From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Peter Wang (王信友)" <peter.wang@mediatek.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yee Lee (李建誼)" <Yee.Lee@mediatek.com>,
"Stanley Chu (朱原陞)" <stanley.chu@mediatek.com>,
"Powen Kao (高伯文)" <Powen.Kao@mediatek.com>,
"Alice Chao (趙珮均)" <Alice.Chao@mediatek.com>
Subject: Re: backport commit ("2bd3b6b75946db2ace06e145d53988e10ed7e99a [v1] scsi: ufs: scsi_get_lba error fix by check cmd opcode") to linux-5.15/linux-5.16/linux-5.17
Date: Thu, 21 Apr 2022 16:16:32 +0200 [thread overview]
Message-ID: <YmFnQNSoEjsousM0@kroah.com> (raw)
In-Reply-To: <PSAPR03MB5605D50B15FEB10D57FBDFF3ECF49@PSAPR03MB5605.apcprd03.prod.outlook.com>
On Thu, Apr 21, 2022 at 01:44:33PM +0000, Peter Wang (王信友) wrote:
> Hi reviewers,
>
>
>
> I suggest to backport
>
> commit "2bd3b6b75946db2ace06e145d53988e10ed7e99a [v1] scsi: ufs: scsi_get_lba error fix by check cmd opcode"
>
> to linux-5.15/linux-5.16/linux-5.17 tree.
>
>
>
> This patch fix scsi_get_lba issue by
>
> https://github.com/torvalds/linux/commit/54815088859fa766c7879a06ee028e0cee4f589e
>
>
>
> commit: 2bd3b6b75946db2ace06e145d53988e10ed7e99a
>
> subject: [v1] scsi: ufs: scsi_get_lba error fix by check cmd opcode
Now queued up, thanks.
greg k-h
parent reply other threads:[~2022-04-21 14:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <PSAPR03MB5605D50B15FEB10D57FBDFF3ECF49@PSAPR03MB5605.apcprd03.prod.outlook.com>]
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=YmFnQNSoEjsousM0@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alice.Chao@mediatek.com \
--cc=Powen.Kao@mediatek.com \
--cc=Yee.Lee@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=stable@vger.kernel.org \
--cc=stanley.chu@mediatek.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.