mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2026-05-24 11:18:52 +03:00
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
This commit is contained in:
@@ -68,12 +68,10 @@ DECLARE_EVENT_CLASS(zfs_removing_class_3,
|
||||
);
|
||||
/* END CSTYLED */
|
||||
|
||||
/* BEGIN CSTYLED */
|
||||
#define DEFINE_REMOVE_FREE_EVENT(name) \
|
||||
#define DEFINE_REMOVE_FREE_EVENT(name) \
|
||||
DEFINE_EVENT(zfs_removing_class_3, name, \
|
||||
TP_PROTO(spa_t *spa, uint64_t offset, uint64_t size), \
|
||||
TP_ARGS(spa, offset, size))
|
||||
/* END CSTYLED */
|
||||
TP_PROTO(spa_t *spa, uint64_t offset, uint64_t size), \
|
||||
TP_ARGS(spa, offset, size))
|
||||
DEFINE_REMOVE_FREE_EVENT(zfs_remove__free__synced);
|
||||
DEFINE_REMOVE_FREE_EVENT(zfs_remove__free__unvisited);
|
||||
|
||||
@@ -107,12 +105,10 @@ DECLARE_EVENT_CLASS(zfs_removing_class_4,
|
||||
__entry->vdev_size, __entry->vdev_txg)
|
||||
);
|
||||
|
||||
/* BEGIN CSTYLED */
|
||||
#define DEFINE_REMOVE_FREE_EVENT_TXG(name) \
|
||||
DEFINE_EVENT(zfs_removing_class_4, name, \
|
||||
TP_PROTO(spa_t *spa, uint64_t offset, uint64_t size,uint64_t txg), \
|
||||
TP_ARGS(spa, offset, size, txg))
|
||||
/* END CSTYLED */
|
||||
TP_PROTO(spa_t *spa, uint64_t offset, uint64_t size,uint64_t txg), \
|
||||
TP_ARGS(spa, offset, size, txg))
|
||||
DEFINE_REMOVE_FREE_EVENT_TXG(zfs_remove__free__inflight);
|
||||
|
||||
#endif /* _TRACE_VDEV_H */
|
||||
|
||||
Reference in New Issue
Block a user