[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170822100319.hgmhmhj45twwxb2w@mwanda>
Date: Tue, 22 Aug 2017 13:03:20 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Rishabh Hardas <rishabhhardas@...il.com>
Cc: Joe Perches <joe@...ches.com>, devel@...verdev.osuosl.org,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
rjosephwright@...il.com, linux@...f-Entwicklungen.de,
colin.king@...onical.com
Subject: Re: [PATCH v2 1/4] staging: pi433: Style fix - Correct long lines
On Tue, Aug 22, 2017 at 02:57:49PM +0530, Rishabh Hardas wrote:
> On Sat, Aug 19, 2017 at 09:47:28PM -0700, Joe Perches wrote:
> > On Wed, 2017-08-16 at 10:31 +0300, Dan Carpenter wrote:
> > > 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.
> >
> > The original wasn't any good either.
> >
> > It'd be better to avoid the macros altogether
> > as almost all are use-once.
> >
> >
> So should I keep this as it is or remove the macros ?
> Because as Dan said the corrections that I made aren't goo either.
>
Find a way to correct it which makes the code more readable than it was
before.
regards,
dan carpenter
Powered by blists - more mailing lists