mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <Avri.Altman@wdc.com>,
	"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 2/2] scsi: ufs: Add HCI capabilities sysfs group
Date: Thu, 8 Aug 2024 10:08:43 -0700	[thread overview]
Message-ID: <c5715a05-c6da-4e7d-abb7-87db0756dc10@acm.org> (raw)
In-Reply-To: <DM6PR04MB657591C5FD3C16AB0864FA6EFCB92@DM6PR04MB6575.namprd04.prod.outlook.com>

On 8/8/24 4:32 AM, Avri Altman wrote:
> So I am wondering if having something like the below is acceptable?
> /sys/devices/platform/<platform-specific-path>/ufshci_capabilities

This is also fine with me:

/sys/devices/platform/.../ufshci_capabilities

Thanks,

Bart.

  reply	other threads:[~2024-08-08 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04  7:21 [PATCH v2 0/2] scsi: ufs: Add host " Avri Altman
2024-08-04  7:21 ` [PATCH v2 1/2] scsi: ufs: Prepare to add HCI capabilities sysfs Avri Altman
2024-08-06 22:01   ` Bart Van Assche
2024-08-07  5:41     ` Avri Altman
2024-08-07 20:48   ` Bart Van Assche
2024-08-04  7:21 ` [PATCH v2 2/2] scsi: ufs: Add HCI capabilities sysfs group Avri Altman
2024-08-07 20:55   ` Bart Van Assche
2024-08-08 11:32     ` Avri Altman
2024-08-08 17:08       ` Bart Van Assche [this message]
     [not found] ` <CGME20240804072309epcas2p2309ebc15f20ca598a91fe30a3245200f@epcms2p1>
2024-08-06  2:04   ` [PATCH v2 1/2] scsi: ufs: Prepare to add HCI capabilities sysfs Keoseong Park
     [not found] ` <CGME20240804072321epcas2p3fbbda7858fe25be16ef6acb64b7a524e@epcms2p3>
2024-08-06  2:06   ` [PATCH v2 2/2] scsi: ufs: Add HCI capabilities sysfs group Keoseong Park

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=c5715a05-c6da-4e7d-abb7-87db0756dc10@acm.org \
    --to=bvanassche@acm.org \
    --cc=Avri.Altman@wdc.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 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®