From: Bart Van Assche <bvanassche@acm.org>
To: Hongjie Fang <hongjiefang@asrmicro.com>,
avri.altman@wdc.com, peter.wang@mediatek.com, beanhuo@micron.com,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: core: Add a vop to handle vendor specific ops
Date: Thu, 19 Mar 2026 14:12:42 -0700 [thread overview]
Message-ID: <64cc22ec-4d43-45c0-b63f-0401776f79a7@acm.org> (raw)
In-Reply-To: <20260319093839.1854051-1-hongjiefang@asrmicro.com>
On 3/19/26 2:38 AM, Hongjie Fang wrote:
> add a vop to allow some vendors to do some additional ops
> for some interrupts if necessary.
UFS patches should be sent to Martin K. Petersen and should be Cc-ed to
the linux-scsi mailing list. Additionally, a patch description should
not only explain what has been changed but also why a change is being
mode. "to do some additional ops for some interrupts if necessary" is
too vague.
> @@ -7141,6 +7141,8 @@ static irqreturn_t ufshcd_sl_intr(struct ufs_hba *hba, u32 intr_status)
> {
> irqreturn_t retval = IRQ_NONE;
>
> + ufshcd_vops_vendor_intr(hba);
Why to call this code from inside ufshcd_sl_intr() instead of from the
ufshcd_sl_intr() caller?
> @@ -380,6 +381,7 @@ struct ufs_hba_variant_ops {
> int (*config_esi)(struct ufs_hba *hba);
> void (*config_scsi_dev)(struct scsi_device *sdev);
> u32 (*freq_to_gear_speed)(struct ufs_hba *hba, unsigned long freq);
> + void (*vendor_intr)(struct ufs_hba *hba);
> };
Where is the implementation of .vendor_intr? I don't see any
implementation of that new callback in this patch. Please always submit
at least one implementation of a new vendor operation together with the
patch that adds the new vendor operation.
Thanks,
Bart.
next prev parent reply other threads:[~2026-03-19 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 9:38 Hongjie Fang
2026-03-19 21:12 ` Bart Van Assche [this message]
2026-03-21 3:34 ` Fang Hongjie(方洪杰)
2026-03-23 17:29 ` Bart Van Assche
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=64cc22ec-4d43-45c0-b63f-0401776f79a7@acm.org \
--to=bvanassche@acm.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=hongjiefang@asrmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®