LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Kiwoong Kim <kwmad.kim@samsung.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
alim.akhtar@samsung.com, avri.altman@wdc.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, beanhuo@micron.com,
cang@codeaurora.org, adrian.hunter@intel.com, sc.suh@samsung.com,
hy50.seo@samsung.com, sh425.lee@samsung.com,
bhoon95.kim@samsung.com
Subject: Re: [RFC PATCH v1 0/2] scsi: ufs: introduce vendor isr
Date: Fri, 6 Aug 2021 09:14:54 -0700 [thread overview]
Message-ID: <b3c18b34-2108-abfa-54ca-096a3eb31318@acm.org> (raw)
In-Reply-To: <cover.1628231581.git.kwmad.kim@samsung.com>
On 8/5/21 11:34 PM, Kiwoong Kim wrote:
> This patch is to activate some interrupt sources
> that aren't defined in UFSHCI specifications. Those
> purpose could be error handling, workaround or whatever.
How about extending the UFS spec instead of adding a non-standard
mechanism in a driver that is otherwise based on a standard?
Thanks,
Bart.
next prev parent reply other threads:[~2021-08-06 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210806064923epcas2p13dd6b442eed02404d87684afd9c1b229@epcas2p1.samsung.com>
2021-08-06 6:34 ` Kiwoong Kim
[not found] ` <CGME20210806064924epcas2p4572538fd1fa7a73d8262737e38a9b537@epcas2p4.samsung.com>
2021-08-06 6:34 ` [RFC PATCH v1 1/2] " Kiwoong Kim
2021-08-06 16:18 ` Bart Van Assche
2021-08-09 7:33 ` Kiwoong Kim
[not found] ` <CGME20210806064925epcas2p2ba7e711758614384c17648d4924d025c@epcas2p2.samsung.com>
2021-08-06 6:34 ` [RFC PATCH v1 2/2] scsi: ufs: ufs-exynos: implement exynos isr Kiwoong Kim
2021-08-06 16:37 ` Bart Van Assche
2021-08-09 7:31 ` Kiwoong Kim
2021-08-06 16:14 ` Bart Van Assche [this message]
2021-08-08 5:56 ` [RFC PATCH v1 0/2] scsi: ufs: introduce vendor isr Avri Altman
2021-08-09 7:46 ` Kiwoong Kim
2021-08-09 16:08 ` Bart Van Assche
2021-08-13 5:31 ` Kiwoong Kim
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=b3c18b34-2108-abfa-54ca-096a3eb31318@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bhoon95.kim@samsung.com \
--cc=cang@codeaurora.org \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@samsung.com \
--subject='Re: [RFC PATCH v1 0/2] scsi: ufs: introduce vendor isr' \
/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
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).