From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752980AbdBCJvT (ORCPT ); Fri, 3 Feb 2017 04:51:19 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:44222 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752954AbdBCJvR (ORCPT ); Fri, 3 Feb 2017 04:51:17 -0500 Date: Fri, 3 Feb 2017 10:51:21 +0100 From: Greg KH To: Arushi Cc: w.d.hubbs@gmail.com, devel@driverdev.osuosl.org, kirk@reisers.ca, hris@the-brannons.com, speakup@linux-speakup.org, linux-kernel@vger.kernel.org, samuel.thibault@ens-lyon.org Subject: Re: [PATCH v4] staging: rtl8192e: Aligning the * on each line in block comments Message-ID: <20170203095121.GA24767@kroah.com> References: <20170203052611.GA11318@arushi-HP-Pavilion-Notebook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170203052611.GA11318@arushi-HP-Pavilion-Notebook> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 03, 2017 at 10:56:12AM +0530, Arushi wrote: > This patch fixes the issue by aligning the * on each line in block comments. > [Patch v1] is rejected as the changes done is not following the linux > coding style and [Patch v2] is rejected because forgot to mention the > cause of rejection of [Patch v1].The cause of rejection of [Patch v3] is > that the mention of the cause was not in the correct format. > > Signed-off-by: Arushi Note, I need a "full" name here, not just one name, unless this is what you use to sign legal documents. Also, you sent two different copies of this same patch, which one am I supposed to take? > > --- > > In the [patch v1] to allign the * on each line in block was not correct > as it is also not following the correct coding style of kernel so it got > rejected and the details of all the other patch versions is given above. This is v4, what changed in v2, v3, and v4? Please list all of the changes, there is lots of good examples of how to do this on the mailing list and in the documentation. thanks, greg k-h