mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Arthur Simchaev <arthur.simchaev@wdc.com>, martin.petersen@oracle.com
Cc: avri.altman@wdc.com, Avi.Shchislowski@wdc.com,
	beanhuo@micron.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND v2] ufs: core: Add support for qTimestamp attribute
Date: Wed, 28 Jun 2023 15:50:44 -0700	[thread overview]
Message-ID: <896abe03-4fcd-003f-1273-209daafc5635@acm.org> (raw)
In-Reply-To: <20230626103320.8737-1-arthur.simchaev@wdc.com>

On 6/26/23 03:33, Arthur Simchaev wrote:
> +/**
> + * struct utp_upiu_query_v4_0 - upiu request buffer structure for
> + * query request >= UFS 4.0 spec.
> + * @opcode: command to perform B-0
> + * @idn: a value that indicates the particular type of data B-1
> + * @index: Index to further identify data B-2
> + * @selector: Index to further identify data B-3
> + * @osf4: spec field B-5
> + * @osf5: spec field B 6,7
> + * @osf6: spec field DW 8,9
> + * @osf7: spec field DW 10,11
> + */
> +struct utp_upiu_query_v4_0 {
> +	__u8 opcode;
> +	__u8 idn;
> +	__u8 index;
> +	__u8 selector;
> +	__u8 osf3;
> +	__u8 osf4;
> +	__be16 osf5;
> +	__be32 osf6;
> +	__be32 osf7;
> +	__be32 reserved;
> +};

Is this structure useful for user space software? If not, please move it 
into another header file.

Thanks,

Bart.

  parent reply	other threads:[~2023-06-28 22:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 10:33 Arthur Simchaev
2023-06-26 12:36 ` Bean Huo
2023-06-27 11:22   ` Arthur Simchaev
2023-06-28 22:50 ` Bart Van Assche [this message]
2023-06-29 13:58   ` Arthur Simchaev
2023-07-05 10:02     ` Arthur Simchaev
2023-07-05 21:13 ` Bart Van Assche
2023-07-06  1:44   ` Martin K. Petersen
2023-07-11 16:31 ` Martin K. Petersen

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=896abe03-4fcd-003f-1273-209daafc5635@acm.org \
    --to=bvanassche@acm.org \
    --cc=Avi.Shchislowski@wdc.com \
    --cc=arthur.simchaev@wdc.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.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®