From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Orson Zhai <orsonzhai@gmail.com>
Cc: stable@vger.kernel.org, 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: Re: [PATCH 1/2] scsi: ufs: Fix interrupt error message for shared interrupts
Date: Wed, 17 Nov 2021 18:55:28 +0100 [thread overview]
Message-ID: <YZVCEPc1Fu8nee9y@kroah.com> (raw)
In-Reply-To: <1637059711-11746-2-git-send-email-orsonzhai@gmail.com>
On Tue, Nov 16, 2021 at 06:48:30PM +0800, Orson Zhai wrote:
> From: Adrian Hunter <adrian.hunter@intel.com>
>
> [ Upstream commit 6337f58cec030b34ced435b3d9d7d29d63c96e36 ]
>
> The interrupt might be shared, in which case it is not an error for the
> interrupt handler to be called when the interrupt status is zero, so don't
> print the message unless there was enabled interrupt status.
>
> Change-Id: Ic18aa63b43d9479a62e8e664a73e70380669b109
Why is this here? :(
I'll go delete it...
next prev parent reply other threads:[~2021-11-17 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 10:48 [PATCH 0/2] scsi/ufs: Cherry-pick 2 fixes for null pointer into 5.4.y only Orson Zhai
2021-11-16 10:48 ` [PATCH 1/2] scsi: ufs: Fix interrupt error message for shared interrupts Orson Zhai
2021-11-17 17:55 ` Greg Kroah-Hartman [this message]
2021-11-16 10:48 ` [PATCH 2/2] scsi: ufs: Fix tm request when non-fatal error happens Orson Zhai
2021-11-17 17:58 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2020-08-10 13:55 [PATCH 1/2] scsi: ufs: Fix interrupt error message for shared interrupts Adrian Hunter
2020-08-11 12:20 ` Avri Altman
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=YZVCEPc1Fu8nee9y@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=cang@codeaurora.org \
--cc=jaegeuk@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=orson.zhai@gmail.com \
--cc=orson.zhai@unisoc.com \
--cc=orsonzhai@gmail.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 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.