mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Quytelda Kahja <quytelda@tamalin.org>
Cc: gs051095@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: gdm724x: tty: Fix macro argument reuse that could cause side-effects.
Date: Sat, 17 Feb 2018 13:17:41 +0100	[thread overview]
Message-ID: <20180217121741.GC10940@kroah.com> (raw)
In-Reply-To: <20180216222655.23919-1-quytelda@tamalin.org>

On Fri, Feb 16, 2018 at 02:26:55PM -0800, Quytelda Kahja wrote:
> Fix a coding style warning from checkpatch.pl.  Use GNU extensions to create
> references to the results of problem macro arguments when they are evaluated so
> that they can be used safely multiple times.
> 
> Signed-off-by: Quytelda Kahja <quytelda@tamalin.org>
> ---
>  drivers/staging/gdm724x/gdm_tty.c | 24 ++++++++++++++++--------
>  1 file changed, 16 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/staging/gdm724x/gdm_tty.c b/drivers/staging/gdm724x/gdm_tty.c
> index fc7682c18f20..73d39fa86d10 100644
> --- a/drivers/staging/gdm724x/gdm_tty.c
> +++ b/drivers/staging/gdm724x/gdm_tty.c
> @@ -37,14 +37,22 @@
>  
>  #define MUX_TX_MAX_SIZE 2048
>  
> -#define gdm_tty_send(n, d, l, i, c, b) (\
> -	n->tty_dev->send_func(n->tty_dev->priv_dev, d, l, i, c, b))
> -#define gdm_tty_recv(n, c) (\
> -	n->tty_dev->recv_func(n->tty_dev->priv_dev, c))
> -#define gdm_tty_send_control(n, r, v, d, l) (\
> -	n->tty_dev->send_control(n->tty_dev->priv_dev, r, v, d, l))
> -
> -#define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev && gdm->port.count)
> +#define gdm_tty_send(n, d, l, i, c, b)					\
> +	({ typeof(n) n_ = (n);						\
> +		void *priv_dev = n_->tty_dev->priv_dev;			\
> +		n_->tty_dev->send_func(priv_dev, d, l, i, c, b); })
> +#define gdm_tty_recv(n, c)					\
> +	({ typeof(n) n_ = (n);					\
> +		void *priv_dev = n_->tty_dev->priv_dev;		\
> +		n_->tty_dev->recv_func(priv_dev, c); })
> +#define gdm_tty_send_control(n, r, v, d, l)				\
> +	({ typeof(n) n_ = (n);						\
> +		void *priv_dev = n_->tty_dev->priv_dev;			\
> +		n_->tty_dev->send_control(priv_dev, r, v, d, l); })
> +
> +#define GDM_TTY_READY(gdm)						\
> +	({ typeof(gdm) gdm_ = gdm;					\
> +		gdm_ && gdm_->tty_dev && gdm_->port.count; })

Ugh, that's a mess.  How about just replacing the use of these odd
macros with the "real" call instead?  The fact that they are messing
around with the tty_dev call directly is really strange and should be
made a lot more obvious, as that probably needs to be fixed up.

thanks,

greg k-h

  reply	other threads:[~2018-02-17 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 22:26 Quytelda Kahja
2018-02-17 12:17 ` Greg KH [this message]
2018-02-17 21:02   ` Quytelda Kahja

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=20180217121741.GC10940@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gs051095@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quytelda@tamalin.org \
    /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