diff options
author | наб <nabijaczleweli@nabijaczleweli.xyz> | 2022-01-21 16:07:15 +0000 |
---|---|---|
committer | Brian Behlendorf <behlendorf1@llnl.gov> | 2022-01-26 19:38:52 +0000 |
commit | 7ada752a934f79d87fb9ef998455f26fd07f59a7 (patch) | |
tree | fadcb89e9710da5b7ad2d5b6f26c94eb1ca96d50 /module/zfs/zfs_ioctl.c | |
parent | a3fecf4f1059f4afcead0e7a502ffe8babb1e39c (diff) | |
download | src-7ada752a934f79d87fb9ef998455f26fd07f59a7.tar.gz src-7ada752a934f79d87fb9ef998455f26fd07f59a7.zip |
Clean up CSTYLEDs
69 CSTYLED BEGINs remain, appx. 30 of which can be removed if cstyle(1)
had a useful policy regarding
CALL(ARG1,
ARG2,
ARG3);
above 2 lines. As it stands, it spits out *both*
sysctl_os.c: 385: continuation line should be indented by 4 spaces
sysctl_os.c: 385: indent by spaces instead of tabs
which is very cool
Another >10 could be fixed by removing "ulong" &al. handling.
I don't foresee anyone actually using it intentionally
(does it even exist in modern headers? why did it in the first place?).
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Closes #12993
Diffstat (limited to 'module/zfs/zfs_ioctl.c')
-rw-r--r-- | module/zfs/zfs_ioctl.c | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/module/zfs/zfs_ioctl.c b/module/zfs/zfs_ioctl.c index e592734eea09..e004410ea553 100644 --- a/module/zfs/zfs_ioctl.c +++ b/module/zfs/zfs_ioctl.c @@ -7862,10 +7862,8 @@ zfs_kmod_fini(void) tsd_destroy(&zfs_allow_log_key); } -/* BEGIN CSTYLED */ ZFS_MODULE_PARAM(zfs, zfs_, max_nvlist_src_size, ULONG, ZMOD_RW, - "Maximum size in bytes allowed for src nvlist passed with ZFS ioctls"); + "Maximum size in bytes allowed for src nvlist passed with ZFS ioctls"); ZFS_MODULE_PARAM(zfs, zfs_, history_output_max, ULONG, ZMOD_RW, - "Maximum size in bytes of ZFS ioctl output that will be logged"); -/* END CSTYLED */ + "Maximum size in bytes of ZFS ioctl output that will be logged"); |