From: "Hoyoung SEO" <hy50.seo@samsung.com>
To: "'Martin K. Petersen'" <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<jejb@linux.ibm.com>, <beanhuo@micron.com>, <bvanassche@acm.org>,
<bhoon95.kim@samsung.com>, <kwmad.kim@samsung.com>
Subject: RE: [PATCH v2] scsi: ufs: add a variant operation in struct ufs_hba_variant_ops
Date: Fri, 16 Sep 2022 10:59:38 +0900 [thread overview]
Message-ID: <18d501d8c96f$fa5fba00$ef1f2e00$@samsung.com> (raw)
In-Reply-To: <yq1czbw2ihu.fsf@ca-mkp.ca.oracle.com>
> -----Original Message-----
> From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
> Sent: Friday, September 16, 2022 10:55 AM
> To: SEO HOYOUNG
> Cc: 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; bvanassche@acm.org;
> bhoon95.kim@samsung.com; kwmad.kim@samsung.com
> Subject: Re: [PATCH v2] scsi: ufs: add a variant operation in struct
> ufs_hba_variant_ops
>
>
> Seo,
>
> > +static inline void ufshcd_vops_check_int_error(struct ufs_hba *hba,
> > + bool *queue_eh_work)
> > +{
> > + if (hba->vops & hba->vops->check_int_error)
>
> Uhm?
>
I will fixed it.
Thanks.
> > + hba->vops->check_int_error(hba, queue_eh_work); }
> > +
>
> --
> Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-09-16 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220913075407epcas2p1075426e0ef45b6969e50823d59c374d3@epcas2p1.samsung.com>
[not found] ` <sc.suh@samsung.com; hy50.seo@samsung.com;>
2022-09-12 19:37 ` [PATCH v2] scsi: ufs: add a variant operation in struct ufs_hba_variant_ops SEO HOYOUNG
2022-09-15 19:56 ` Bart Van Assche
2022-09-16 1:54 ` Martin K. Petersen
2022-09-16 1:59 ` Hoyoung SEO [this message]
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='18d501d8c96f$fa5fba00$ef1f2e00$@samsung.com' \
--to=hy50.seo@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bhoon95.kim@samsung.com \
--cc=bvanassche@acm.org \
--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 \
/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.