From: Dan Carpenter <dan.carpenter@oracle.com>
To: Rishabh Hardas <rishabhhardas@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, rjosephwright@gmail.com,
linux@Wolf-Entwicklungen.de, colin.king@canonical.com
Subject: Re: [PATCH v2 1/4] staging: pi433: Style fix - Correct long lines
Date: Wed, 16 Aug 2017 10:31:06 +0300 [thread overview]
Message-ID: <20170816073106.vyhezn7f2recdarp@mwanda> (raw)
In-Reply-To: <2adda87146ff5161e33f0379c662908ecc1f3e0a.1501759442.git.rishabhhardas@gmail.com>
On Wed, Aug 16, 2017 at 10:53:18AM +0530, Rishabh Hardas wrote:
> @@ -143,10 +142,13 @@ struct pi433_rx_cfg {
>
> #define PI433_IOC_MAGIC 'r'
>
> -#define PI433_IOC_RD_TX_CFG _IOR(PI433_IOC_MAGIC, PI433_TX_CFG_IOCTL_NR, char[sizeof(struct pi433_tx_cfg)])
> -#define PI433_IOC_WR_TX_CFG _IOW(PI433_IOC_MAGIC, PI433_TX_CFG_IOCTL_NR, char[sizeof(struct pi433_tx_cfg)])
> -
> -#define PI433_IOC_RD_RX_CFG _IOR(PI433_IOC_MAGIC, PI433_RX_CFG_IOCTL_NR, char[sizeof(struct pi433_rx_cfg)])
> -#define PI433_IOC_WR_RX_CFG _IOW(PI433_IOC_MAGIC, PI433_RX_CFG_IOCTL_NR, char[sizeof(struct pi433_rx_cfg)])
> +#define PI433_IOC_RD_TX_CFG _IOR(PI433_IOC_MAGIC, PI433_TX_CFG_IOCTL_NR,\
> + char[sizeof(struct pi433_tx_cfg)])
> +#define PI433_IOC_WR_TX_CFG _IOW(PI433_IOC_MAGIC, PI433_TX_CFG_IOCTL_NR,\
> + char[sizeof(struct pi433_tx_cfg)])
> +#define PI433_IOC_RD_RX_CFG _IOR(PI433_IOC_MAGIC, PI433_RX_CFG_IOCTL_NR,\
> + char[sizeof(struct pi433_rx_cfg)])
> +#define PI433_IOC_WR_RX_CFG _IOW(PI433_IOC_MAGIC, PI433_RX_CFG_IOCTL_NR,\
> + char[sizeof(struct pi433_rx_cfg)])
These don't help readability. The original was better.
regards,
dan carpenter
next prev parent reply other threads:[~2017-08-16 7:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 11:50 [PATCH v2 0/4] staging: pi433: Rename camel case and other style issues Rishabh Hardas
2017-08-03 11:50 ` [PATCH v2 1/4] staging: pi433: Style fix - Correct long lines Rishabh Hardas
2017-08-15 0:42 ` Greg KH
2017-08-16 7:31 ` Dan Carpenter [this message]
2017-08-20 4:47 ` Joe Perches
2017-08-22 9:27 ` Rishabh Hardas
2017-08-22 10:03 ` Dan Carpenter
2017-08-22 10:29 ` Marcus Wolf
2017-08-22 10:43 ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 2/4] staging: pi433: Change Comments Rishabh Hardas
2017-08-16 7:35 ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 3/4] staging: pi433: Renaming Enums Rishabh Hardas
2017-08-16 7:34 ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 4/4] staging: pi433: Remove camel case variable names Rishabh Hardas
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=20170816073106.vyhezn7f2recdarp@mwanda \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@Wolf-Entwicklungen.de \
--cc=rishabhhardas@gmail.com \
--cc=rjosephwright@gmail.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
Powered by JetHome