All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Joe Perches <joe@perches.com>
Cc: Andr? Silva <andre.beat@gmail.com>,
	linville@tuxdriver.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: arlan: fixed coding style issues in arlan-proc.c This is a patch to the arlan-proc.c file that fixes up multiple coding style errors and warnings found by the checkpatch.pl tool Signed-off-by: Andre Silva <andre.beat@gmail.com>
Date: Wed, 10 Mar 2010 19:32:48 -0800	[thread overview]
Message-ID: <20100311033248.GA3832@suse.de> (raw)
In-Reply-To: <1268278090.1674.37.camel@Joe-Laptop.home>

On Wed, Mar 10, 2010 at 07:28:10PM -0800, Joe Perches wrote:
> On Thu, 2010-03-11 at 02:58 +0000, Andr?? Silva wrote:
> > From: Andre Silva <andre.beat@gmail.com>
> 
> Hi Andre.
> 
> When you send a patch, please use a shorter subject
> and add some commentary in the body of the email
> that describes the changes before the patch itself.

He did, it's a "issue" with git-send-email that if you don't have empty
lines, it puts it all on the Subject: line.

I'm used to fixing it up, so no big deal,

greg k-h

  reply	other threads:[~2010-03-11  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  2:58 [PATCH] Staging: arlan: fixed coding style issues in arlan-proc.c This is a patch to the arlan-proc.c file that fixes up multiple coding style errors and warnings found by the checkpatch.pl tool Signed-off-by: Andre Silva <andre.beat@gmail.com> André Silva
2010-03-11  3:28 ` Joe Perches
2010-03-11  3:32   ` Greg KH [this message]
2010-03-11  4:40     ` Joe Perches
2010-03-11  7:09       ` [PATCH] Staging: arlan: fixed coding style issues in arlan-proc.c (etc...) Frans Pop

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=20100311033248.GA3832@suse.de \
    --to=gregkh@suse.de \
    --cc=andre.beat@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.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.