Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

White space changes #2216

Merged
merged 8 commits into from
Mar 12, 2024
Merged

White space changes #2216

merged 8 commits into from
Mar 12, 2024

Conversation

ikegami-t
Copy link
Contributor

Includes some minor changes also. Just split the chagnes from the PR #2188 but deleted the long line string changes.

@ikegami-t
Copy link
Contributor Author

Todo: Change register value output to use the macros NVME_PMRCAP_CMSS and other NVME_***_***.

Copy link
Contributor

@calebsander calebsander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good!

Comment on lines 23 to 27
--offset::
The offset of the property.

-V::
--value:
-V <val>::
--value=<val>::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is inconsistent with --offset, which also takes a value. I see other command arguments that take arguments not having them specified here (e.g. nvme get-property --offset). Why only change this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed it so just fixed.

@@ -3264,20 +3278,21 @@ static void stdout_zns_changed(struct nvme_zns_changed_zone_log *log)

static void stdout_zns_report_zone_attributes(__u8 za, __u8 zai)
{
const char *const recommended_limit[4] = {"","1","2","3"};
const char *const recommended_limit[4] = {"", "1", "2", "3"};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a space between * and const while you're touching this line? const char * const

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes done it.

@ikegami-t ikegami-t force-pushed the white-space branch 2 times, most recently from 6c1db3a to e1843b8 Compare March 3, 2024 04:30
chan_desc = (struct nvme_end_grp_chan_desc *) \
((cap->cap_config_desc[i].egcd[j].nvmsetid[0]) * (sizeof(__u16)*egsets));
chan_desc = (struct nvme_end_grp_chan_desc *)
(sizeof(__u16) * egsets * cap->cap_config_desc[i].egcd[j].nvmsetid[0]);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part should be in the next patch. It's not a white space change thus it should get a proper commit message with it.

sscanf(nvme_ns_get_name(n), "nvme%dn%d", &instance, &head_instance);
if (sscanf(nvme_ns_get_name(n), "nvme%dn%d", &instance, &head_instance) != 2)
return;

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a whitespace change. Should be in a different patch.

le16_to_cpu(cap->cap_config_desc[i].egcd[j].nvmsetid[k]));
}
le16_to_cpu(cap->cap_config_desc[i].egcd[j].nvmsetid[k]));

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split whitespace change and logical changes into separate patches.

-O::
--offset::
-O <offset>::
--offset=<offset>::
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just split the two different changes into two patches. One which fixes the mode settings and one which fixes the offset changes. Thanks.

@igaw
Copy link
Collaborator

igaw commented Mar 7, 2024

A few nitpicks. Could you rebase the series to the latest upstream version when you updating the series? There is merge conflict in nvme-print.c Thanks.

Fix to change space characters for indentation to tab characters.
Delete a space between cast parentheses and variable.

Signed-off-by: Tokunori Ikegami <[email protected]>
Fix for the checkpatch.pl error.

Signed-off-by: Tokunori Ikegami <[email protected]>
All the cases listed adjacently and use only for cases have any body.

Signed-off-by: Tokunori Ikegami <[email protected]>
Note: The long line string and strncpy() warnings are not fixed.

Signed-off-by: Tokunori Ikegami <[email protected]>
To fix linux kernel check patch error.

Signed-off-by: Tokunori Ikegami <[email protected]>
Set the address after NVM set EGSETS - 1 identifier parameter.

Signed-off-by: Tokunori Ikegami <[email protected]>
Only the get-property and set-property commands fixed errors.

Signed-off-by: Tokunori Ikegami <[email protected]>
Those parameters need the <offset> and <val> parameters values.

Signed-off-by: Tokunori Ikegami <[email protected]>
@igaw igaw merged commit 6414c33 into linux-nvme:master Mar 12, 2024
16 checks passed
@igaw
Copy link
Collaborator

igaw commented Mar 12, 2024

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants