From: Greg KH <gregkh@linuxfoundation.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: linux-staging@lists.linux.dev, Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH 4/4] staging: greybus: greybus_firmware: fix long macro lines
Date: Mon, 22 Dec 2025 09:47:00 +0100 [thread overview]
Message-ID: <2025122240-exponent-polyester-f9c3@gregkh> (raw)
In-Reply-To: <20251219063415.46818-5-zhanxusheng@xiaomi.com>
On Fri, Dec 19, 2025 at 02:34:15PM +0800, Zhan Xusheng wrote:
> Break long ioctl macro definitions into multiple lines to satisfy
> checkpatch.pl line-length checks (<100 columns).
>
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
> ---
> drivers/staging/greybus/greybus_firmware.h | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/greybus/greybus_firmware.h b/drivers/staging/greybus/greybus_firmware.h
> index b6042a82ada4..f59a2def3d45 100644
> --- a/drivers/staging/greybus/greybus_firmware.h
> +++ b/drivers/staging/greybus/greybus_firmware.h
> @@ -64,11 +64,16 @@ struct fw_mgmt_ioc_backend_fw_update {
> } __packed;
>
> #define FW_MGMT_IOCTL_BASE 'F'
> -#define FW_MGMT_IOC_GET_INTF_FW _IOR(FW_MGMT_IOCTL_BASE, 0, struct fw_mgmt_ioc_get_intf_version)
> -#define FW_MGMT_IOC_GET_BACKEND_FW _IOWR(FW_MGMT_IOCTL_BASE, 1, struct fw_mgmt_ioc_get_backend_version)
> -#define FW_MGMT_IOC_INTF_LOAD_AND_VALIDATE _IOWR(FW_MGMT_IOCTL_BASE, 2, struct fw_mgmt_ioc_intf_load_and_validate)
> -#define FW_MGMT_IOC_INTF_BACKEND_FW_UPDATE _IOWR(FW_MGMT_IOCTL_BASE, 3, struct fw_mgmt_ioc_backend_fw_update)
> -#define FW_MGMT_IOC_SET_TIMEOUT_MS _IOW(FW_MGMT_IOCTL_BASE, 4, unsigned int)
> +#define FW_MGMT_IOC_GET_INTF_FW \
> + _IOR(FW_MGMT_IOCTL_BASE, 0, struct fw_mgmt_ioc_get_intf_version)
> +#define FW_MGMT_IOC_GET_BACKEND_FW \
> + _IOWR(FW_MGMT_IOCTL_BASE, 1, struct fw_mgmt_ioc_get_backend_version)
> +#define FW_MGMT_IOC_INTF_LOAD_AND_VALIDATE \
> + _IOWR(FW_MGMT_IOCTL_BASE, 2, struct fw_mgmt_ioc_intf_load_and_validate)
> +#define FW_MGMT_IOC_INTF_BACKEND_FW_UPDATE \
> + _IOWR(FW_MGMT_IOCTL_BASE, 3, struct fw_mgmt_ioc_backend_fw_update)
> +#define FW_MGMT_IOC_SET_TIMEOUT_MS \
> + _IOW(FW_MGMT_IOCTL_BASE, 4, unsigned int)
The originals are fine, ioctls are messy, it's good to see them all on
one line usually.
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-22 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 6:34 [PATCH 0/4] greybus: staging fixes and cleanups Zhan Xusheng
2025-12-19 6:34 ` [PATCH 1/4] staging: greybus: spilib: fix function parameter indentation Zhan Xusheng
2025-12-22 8:45 ` Greg KH
2025-12-19 6:34 ` [PATCH 2/4] staging: greybus: audio: avoid macro with side effects Zhan Xusheng
2025-12-22 8:46 ` Greg KH
2025-12-19 6:34 ` [PATCH 3/4] staging: greybus: gb-camera: use BIT() macro and fix formatting Zhan Xusheng
2025-12-22 8:46 ` Greg KH
2025-12-19 6:34 ` [PATCH 4/4] staging: greybus: greybus_firmware: fix long macro lines Zhan Xusheng
2025-12-22 8:47 ` Greg KH [this message]
2025-12-22 15:40 ` [PATCH 1/4] staging: greybus: gb-camera: use BIT() macro and fix formatting Zhan Xusheng
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=2025122240-exponent-polyester-f9c3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.