From: Bart Van Assche <bvanassche@acm.org>
To: Arthur Simchaev <Arthur.Simchaev@wdc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "beanhuo@micron.com" <beanhuo@micron.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] include: uapi: scsi: Change utp_upiu_query struct
Date: Mon, 27 Feb 2023 08:59:41 -0800 [thread overview]
Message-ID: <21f73bfd-1d91-106f-d3a8-eb4674c517e6@acm.org> (raw)
In-Reply-To: <BY5PR04MB632717453EB0D403388B4F1EEDAF9@BY5PR04MB6327.namprd04.prod.outlook.com>
On 2/27/23 08:03, Arthur Simchaev wrote:
>>>
>>> */
>>> struct utp_upiu_query {
>>> __u8 opcode;
>>> __u8 idn;
>>> __u8 index;
>>> __u8 selector;
>>> - __be16 reserved_osf;
>>> - __be16 length;
>>> - __be32 value;
>>> - __be32 reserved[2];
>>> + __u8 osf3;
>>> + __u8 osf4;
>>> + __be16 osf5;
>>> + __be32 osf6;
>>> + __be32 osf7;
>>> };
>> All changes in UAPI headers must be backwards compatible. The above doesn't look like a backwards compatible change to me.
>
> This API was originally invented to support ufs-bsg.
> AFAIK, ufs-utils is the only app that makes use of this API,
> and it doesn't dig into struct utp_upiu_query inner fields.
That does not match what I see. I see that code in ufs-utils accesses
the 'length' and 'value' members of the above data structure.
Please follow the rules for UAPI header files.
Thanks,
Bart.
next prev parent reply other threads:[~2023-02-27 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:12 [PATCH 0/2] ufs: core: Add support for qTimestamp attribute Arthur Simchaev
2023-02-22 15:12 ` [PATCH 1/2] include: uapi: scsi: Change utp_upiu_query struct Arthur Simchaev
2023-02-22 15:25 ` Bart Van Assche
2023-02-27 16:03 ` Arthur Simchaev
2023-02-27 16:59 ` Bart Van Assche [this message]
2023-03-01 9:46 ` Arthur Simchaev
2023-03-01 18:44 ` Bart Van Assche
2023-03-02 7:52 ` Arthur Simchaev
2023-02-23 2:23 ` kernel test robot
2023-02-22 15:12 ` [PATCH 2/2] ufs: core: Providing Timestamp information to the device Arthur Simchaev
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=21f73bfd-1d91-106f-d3a8-eb4674c517e6@acm.org \
--to=bvanassche@acm.org \
--cc=Arthur.Simchaev@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®