mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] scsi: ufs: critical health condition
Date: Wed, 5 Feb 2025 19:07:32 +0000	[thread overview]
Message-ID: <DM6PR04MB6575FACB152A64BDA4B4F5E8FCF72@DM6PR04MB6575.namprd04.prod.outlook.com> (raw)
In-Reply-To: <9ebbd6d9-149f-43cb-b188-bd3a6125654f@acm.org>

> On 2/4/25 6:31 AM, Avri Altman wrote:
> > +static ssize_t critical_health_show(struct device *dev,
> > +                                 struct device_attribute *attr, char
> > +*buf) {
> > +     struct ufs_hba *hba = dev_get_drvdata(dev);
> > +
> > +     return sysfs_emit(buf, "%d\n", hba->dev_info.critical_health); }
> 
> Hi Avri,
> 
> My understanding is that the UFS 4.1 standard supports reporting a critical
> health event repeatedly while this patch does not allow users to figure out
> whether a critical event has been reported once or repeatedly. Has it been
> considered to report the number of times a critical health event has been
> reported by a UFS device instead of only one bit of information?
Done.

Thanks,
Avri

> 
> Thanks,
> 
> Bart.

  parent reply	other threads:[~2025-02-05 19:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 14:31 Avri Altman
2025-02-05 18:00 ` Bart Van Assche
2025-02-05 18:04   ` Avri Altman
2025-02-05 19:07   ` Avri Altman [this message]
2025-02-06  8:54     ` Avri Altman
2025-02-06 15:54       ` Bart Van Assche
2025-02-06 17:47         ` Avri Altman
2025-02-06 18:08           ` Bart Van Assche
2025-02-06 18:25             ` 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=DM6PR04MB6575FACB152A64BDA4B4F5E8FCF72@DM6PR04MB6575.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --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 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®