public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: John Church <j.church@ymail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, georgiana.chelu93@gmail.com,
	waydi1@gmail.com
Subject: Re: [PATCH] Staging: android: fix coding style issue in timed_gpio.c
Date: Wed, 7 May 2014 11:41:56 +0300	[thread overview]
Message-ID: <20140507084156.GX26890@mwanda> (raw)
In-Reply-To: <5369D165.1080400@ymail.com>

On Wed, May 07, 2014 at 07:23:33AM +0100, John Church wrote:
> This patch fixes a coding style issue. It modifies a single line
> that was over 80 characters long.
> 
> Thanks,
> John

> Signed-off-by: John Church <j.church@ymail.com>

This patch isn't sent in the correct way.  Use git send-email or
read Documentation/email-clients.txt.  Send the patch to yourself.
Save it as raw text including headers and everything.
`cat raw_email.txt | git am`.  Review the log with "git log -p".  When
that looks good then resend it to the list.

> 
> --- linux-next/drivers/staging/android/timed_gpio.c.orig	2014-05-07 00:20:50.429090320 +0100
> +++ linux-next/drivers/staging/android/timed_gpio.c	2014-05-07 00:22:09.204795052 +0100
> @@ -92,7 +92,7 @@ static int timed_gpio_probe(struct platf
>  		return -EBUSY;
>  
>  	gpio_data = devm_kzalloc(&pdev->dev,
> -				sizeof(struct timed_gpio_data) * pdata->num_gpios,
> +			sizeof(struct timed_gpio_data) * pdata->num_gpios,
>  				GFP_KERNEL);

To be honest, I prefered the original because everything lined up nicely
in the original.  Now it just looks whacky.

regards,
dan carpenter

>  	if (!gpio_data)
>  		return -ENOMEM;


           reply	other threads:[~2014-05-07  8:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5369D165.1080400@ymail.com>]

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=20140507084156.GX26890@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=georgiana.chelu93@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=j.church@ymail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waydi1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox