All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi <arushisinghal19971997@gmail.com>
Cc: w.d.hubbs@gmail.com, devel@driverdev.osuosl.org, kirk@reisers.ca,
	speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
	samuel.thibault@ens-lyon.org, chris@the-brannons.com
Subject: Re: [PATCH v6] staging: rtl8192e: Aligning the * on each line in block comments
Date: Fri, 10 Feb 2017 15:04:06 +0100	[thread overview]
Message-ID: <20170210140406.GD28966@kroah.com> (raw)
In-Reply-To: <20170209122311.GA1386@arushi-HP-Pavilion-Notebook>

On Thu, Feb 09, 2017 at 05:53:11PM +0530, Arushi wrote:
> This patch fixes the issue by aligning the * on each line in block comments.
> 
> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>

Your "From:" line in your email does not match this name here, please
fix up and try again.

Also, please properly wrap your changelog lines at 72 columns.

> ---
> [Patch v1] is rejected as the changes done is not correct and is not following the linux kernel coding style in file drivers/staging/speakup/speakup_decpc.c as * on each line in block was not correctly alligned.
> [Patch v2] is rejected for not to mention the cause of rejection of [Patch v1] but warnings is corrected.
> In [Patch v3] mention of the cause was not in the correct format and is not descriptive.
> In [Patch v4] didn't send patch message to all the list members so asked to again repatch it.
> In [Patch v5] in description is not given with proper line-feeds.

Also wrap these properly.

thanks,

greg k-h

      reply	other threads:[~2017-02-10 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 12:23 [PATCH v6] staging: rtl8192e: Aligning the * on each line in block comments Arushi
2017-02-10 14:04 ` Greg KH [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=20170210140406.GD28966@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arushisinghal19971997@gmail.com \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@gmail.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 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.