All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <mike.rapoport@gmail.com>
To: Sakshi Bansal <sakshi.april5@gmail.com>
Cc: gregkh@linuxfoundation.org, shraddha.6596@gmail.com,
	mravindr@visteon.com, tolga.ceylan@gmail.com, wsa@the-dreams.de,
	joe@perches.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: netlogic: xlr_net.h: fixedcoding stly warnings
Date: Thu, 15 Oct 2015 13:14:23 +0300	[thread overview]
Message-ID: <20151015101423.GA3620@zed.strato> (raw)
In-Reply-To: <20151014135930.GA22782@localhost.localdomain>

On Wed, Oct 14, 2015 at 07:29:30PM +0530, Sakshi Bansal wrote:
> Fixed block comments usage of * on subsequent lines
> 
> Signed-off-by: Sakshi Bansal <sakshi.april5@gmail.com>
> ---
>  drivers/staging/netlogic/xlr_net.h | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Please fix the patch subject. There's a space missing in "fixed coding"
and "stly" should have been "style"
 
> diff --git a/drivers/staging/netlogic/xlr_net.h b/drivers/staging/netlogic/xlr_net.h
> index 2f65ec5..7ae8874 100644
> --- a/drivers/staging/netlogic/xlr_net.h
> +++ b/drivers/staging/netlogic/xlr_net.h
> @@ -999,7 +999,8 @@
>  #define MAC_CRC_LEN                     4
>  #define MAX_NUM_MSGRNG_STN_CC           128
>  #define MAX_MSG_SND_ATTEMPTS		100	/* 13 stns x 4 entry msg/stn +
> -						   headroom */
> +						 * headroom
> +						 */
>  
>  #define MAC_FRIN_TO_BE_SENT_THRESHOLD   16
>  
> -- 
> 2.1.0
> 
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

      reply	other threads:[~2015-10-15 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 13:59 [PATCH] staging: netlogic: xlr_net.h: fixedcoding stly warnings Sakshi Bansal
2015-10-15 10:14 ` Mike Rapoport [this message]

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=20151015101423.GA3620@zed.strato \
    --to=mike.rapoport@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mravindr@visteon.com \
    --cc=sakshi.april5@gmail.com \
    --cc=shraddha.6596@gmail.com \
    --cc=tolga.ceylan@gmail.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 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.