All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Maret <mathieu.maret@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	pe1dnn@amsat.org
Subject: Re: [PATCH 4/5] staging: wlags49_h2: Correct macro style in wl_netdev.c
Date: Wed, 19 Mar 2014 09:53:40 -0700	[thread overview]
Message-ID: <20140319165340.GA27769@kroah.com> (raw)
In-Reply-To: <CA+6LquBzTYau34Xrq7j6OitZ0kFw7gvYepdTYJ9697r9XZNcSw@mail.gmail.com>

On Wed, Mar 19, 2014 at 05:42:43PM +0100, Mathieu Maret wrote:
> 
> Le 19 mars 2014 16:34, "Greg KH" <gregkh@linuxfoundation.org> a écrit :
> >
> > On Wed, Mar 19, 2014 at 09:20:34AM +0100, Mathieu Maret wrote:
> > > Multi statement macro should use do{}while(0)
> > >
> > > Signed-off-by: Mathieu Maret <mathieu.maret@gmail.com>
> > > ---
> > >  drivers/staging/wlags49_h2/wl_netdev.c | 8 +++++---
> > >  1 file changed, 5 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/staging/wlags49_h2/wl_netdev.c b/drivers/staging/
> wlags49_h2/wl_netdev.c
> > > index 255d291..6455956 100644
> > > --- a/drivers/staging/wlags49_h2/wl_netdev.c
> > > +++ b/drivers/staging/wlags49_h2/wl_netdev.c
> > > @@ -107,9 +107,11 @@
> > >   * macros
> > >  
> ******************************************************************************/
> > >  #define BLOCK_INPUT(buf, len) \
> > > -    desc->buf_addr = buf; \
> > > -    desc->BUF_SIZE = len; \
> > > -    status = hcf_rcv_msg(&(lp->hcfCtx), desc, 0)
> > > +     do { \
> > > +             desc->buf_addr = buf; \
> > > +             desc->BUF_SIZE = len; \
> > > +             status = hcf_rcv_msg(&(lp->hcfCtx), desc, 0) \
> A ";" is missing here
> > > +     } while (0)
> > >
> > >  #define BLOCK_INPUT_DMA(buf, len) memcpy( buf, desc_next->buf_addr, pktlen
> )
> > >
> >
> > You didn't test-build the code after making this change, as this patch
> > breaks the build into lots of tiny pieces :(
> >
> > Please ALWAYS test your patches.
> >
> > I've applied the first 3 patches, please fix this one up (if it's even
> > possible, hint, I don't think it is...) and resend the remaining
> > patches.
> >
> > thanks,
> >
> > greg k-h
> Hi,
> 
> Very sorry for that. I've mess something in my config file and this file is not
> compiled ...  So newbie ...
> 
> Anyway, it's still very strange, because this macro is not used.
> The error may come from the fact that the last line miss a ";"

If the macro isn't used, just delete it then :)

> When fixed I should repost with "patch V2" in the subject?

Please do so.

thanks,

greg k-h

  parent reply	other threads:[~2014-03-19 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  8:20 [PATCH 1/5] staging: wlags49_h2: reindent wl_netdev.c Mathieu Maret
2014-03-19  8:20 ` [PATCH 2/5] staging: wlags49_h2: remove commented code in wl_netdev.c Mathieu Maret
2014-03-19  8:20 ` [PATCH 3/5] staging: wlags49_h2: Correct comment style " Mathieu Maret
2014-03-19  8:20 ` [PATCH 4/5] staging: wlags49_h2: Correct macro " Mathieu Maret
2014-03-19 15:36   ` Greg KH
     [not found]     ` <CA+6LquBzTYau34Xrq7j6OitZ0kFw7gvYepdTYJ9697r9XZNcSw@mail.gmail.com>
2014-03-19 16:53       ` Greg KH [this message]
2014-03-19  8:20 ` [PATCH 5/5] staging: wlags49_h2: Correct coding " Mathieu Maret

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=20140319165340.GA27769@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.maret@gmail.com \
    --cc=pe1dnn@amsat.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 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.