public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chetan Sethi <cpsethi369@gmail.com>
Cc: devel@driverdev.osuosl.org, punitvara@gmail.com,
	wsa@the-dreams.de, mattkilgore12@gmail.com,
	linux-kernel@vger.kernel.org, weiyongjun1@huawei.com,
	shiva@exdev.nl, bhumirks@gmail.com
Subject: Re: [PATCH v3 2/6] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses
Date: Fri, 24 Feb 2017 18:07:21 +0100	[thread overview]
Message-ID: <20170224170721.GA7142@kroah.com> (raw)
In-Reply-To: <1487324859-29056-1-git-send-email-cpsethi369@gmail.com>

On Fri, Feb 17, 2017 at 06:47:39PM +0900, Chetan Sethi wrote:
> This is 02nd patch to file ks_wlan.h file fixing error of enclosing
> complex macro value in parentheses

No need to have the "This is the XXX patch..." in the changelog text,
you don't see that in any other commit logs, right?

> 
> Signed-off-by: Chetan Sethi <cpsethi369@gmail.com>
> ---
> v2:
>  - split multiple changes across different patches
> v3:
>  - mentioned patch revision in subject
>  - incorporated review comment of correct indentation for do statement
> 
>  drivers/staging/ks7010/ks_wlan.h | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/ks7010/ks_wlan.h b/drivers/staging/ks7010/ks_wlan.h
> index 668202d..33d6b28 100644
> --- a/drivers/staging/ks7010/ks_wlan.h
> +++ b/drivers/staging/ks7010/ks_wlan.h
> @@ -36,8 +36,10 @@
>  
>  #ifdef KS_WLAN_DEBUG
>  #define DPRINTK(n, fmt, args...) \
> -                 if (KS_WLAN_DEBUG > (n)) \
> -			printk(KERN_NOTICE "%s: "fmt, __FUNCTION__, ## args)
> +        do { \

Always run checkpatch on your patches so you don't get a grumpy
maintainer telling you to run your patches through checkpatch!

Please fix up all 3 of these and resend.

thanks,

greg k-h

  reply	other threads:[~2017-02-24 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170216182800.GA30761@kroah.com>
2017-02-17  9:46 ` [PATCH v3 1/6] staging: ks7010: fixed warning of avoiding line over 80 characters Chetan Sethi
2017-02-17  9:47   ` [PATCH v3 2/6] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses Chetan Sethi
2017-02-24 17:07     ` Greg KH [this message]
2017-02-17  9:48   ` [PATCH v3 3/6] staging: ks7010: fix coding style issue of using tabs instead of spaces Chetan Sethi
2017-02-17  9:48   ` [PATCH v3 4/6] drivers: staging: fix coding style issue of using pr_notice instead of printk Chetan Sethi
2017-02-24 17:47     ` Greg KH
2017-02-17  9:49   ` [PATCH v3 5/6] drivers: staging: fix coding style issue of using __func__ instead of __FUNCTION__ Chetan Sethi
2017-02-17  9:49   ` [PATCH v3 6/6] drivers: staging: fix coding style issue of aligning comments properly Chetan Sethi

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=20170224170721.GA7142@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bhumirks@gmail.com \
    --cc=cpsethi369@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattkilgore12@gmail.com \
    --cc=punitvara@gmail.com \
    --cc=shiva@exdev.nl \
    --cc=weiyongjun1@huawei.com \
    --cc=wsa@the-dreams.de \
    /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