stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Orson Zhai <orsonzhai@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>, Can Guo <cang@codeaurora.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Avri Altman <avri.altman@wdc.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	orson.zhai@gmail.com, Orson Zhai <orson.zhai@unisoc.com>
Subject: [PATCH V2 0/2] scsi/ufs: Cherry-pick 2 fixes for null pointer into 5.4.y only
Date: Thu, 18 Nov 2021 22:07:00 +0800	[thread overview]
Message-ID: <1637244422-29190-1-git-send-email-orsonzhai@gmail.com> (raw)

From: Orson Zhai <orson.zhai@unisoc.com>

Hi Greg,

Change v1->v2:

- Remove Change-id in commit message.
- Fix build error for one struct member missing.

I am sorry for my careless about not testing for build before submitting.

-----

Following 2 patches were merged into 5.10.y but not in 5.4.y.
We've found kernel crashes on our devices with 5.4 stable caused by missing them.

Please feel free to add them into the stable queue for 5.4.y if no issue.

Thanks,
Orson

Adrian Hunter (1):
  scsi: ufs: Fix interrupt error message for shared interrupts

Jaegeuk Kim (1):
  scsi: ufs: Fix tm request when non-fatal error happens

 drivers/scsi/ufs/ufshcd.c | 18 +++++++++++++-----
 1 file changed, 13 insertions(+), 5 deletions(-)

-- 
2.7.4


             reply	other threads:[~2021-11-18 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 14:07 Orson Zhai [this message]
2021-11-18 14:07 ` [PATCH v2 1/2] scsi: ufs: Fix interrupt error message for shared interrupts Orson Zhai
2021-11-18 14:07 ` [PATCH v2 2/2] scsi: ufs: Fix tm request when non-fatal error happens Orson Zhai
2021-11-18 14:16 ` [PATCH V2 0/2] scsi/ufs: Cherry-pick 2 fixes for null pointer into 5.4.y only Greg Kroah-Hartman

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=1637244422-29190-1-git-send-email-orsonzhai@gmail.com \
    --to=orsonzhai@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=avri.altman@wdc.com \
    --cc=cang@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaegeuk@kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=orson.zhai@gmail.com \
    --cc=orson.zhai@unisoc.com \
    --cc=sashal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).