public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: "Milan P. Gandhi" <mgandhi@redhat.com>
Cc: Johannes Thumshirn <jth@kernel.org>,
	kernel-janitors@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Remove white spaces from fcoe.h
Date: Mon, 05 Jun 2017 09:18:48 +0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1706051118090.2010@hadrien> (raw)
In-Reply-To: <0f8b6a7b-c1d2-bc95-7970-7572991495cb@redhat.com>



On Mon, 5 Jun 2017, Milan P. Gandhi wrote:

> Remove the white spaces in do/while loop used for checking fcoe
> debug logging

Is it converting spaces to tabs?  If so, saying that would be clearer.

julia

>
> Signed-off-by: Milan P. Gandhi <mgandhi@redhat.com>
> ---
>  drivers/scsi/fcoe/fcoe.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/fcoe/fcoe.h b/drivers/scsi/fcoe/fcoe.h
> index 6aa4820..7406376 100644
> --- a/drivers/scsi/fcoe/fcoe.h
> +++ b/drivers/scsi/fcoe/fcoe.h
> @@ -46,7 +46,7 @@ extern unsigned int fcoe_debug_logging;
>  #define FCOE_NETDEV_LOGGING 0x02 /* Netdevice logging */
>
>  #define FCOE_CHECK_LOGGING(LEVEL, CMD)					\
> -do {                                                            	\
> +do {									\
>  	if (unlikely(fcoe_debug_logging & LEVEL))			\
>  		do {							\
>  			CMD;						\
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2017-06-05  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  8:52 [PATCH] Remove white spaces from fcoe.h Milan P. Gandhi
2017-06-05  9:18 ` Julia Lawall [this message]
2017-06-05  9:54   ` Milan P. Gandhi

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=alpine.DEB.2.20.1706051118090.2010@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=jth@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mgandhi@redhat.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