All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: rcodin <ronit.crj@gmail.com>
Cc: arve@android.com, riandrews@android.com, sumit.semwal@linaro.org,
	mitchelh@codeaurora.org, tranmanphong@gmail.com,
	elfring@users.sourceforge.net, linux@rasmusvillemoes.dk,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: ion: fixed a blank line after declarations coding style issue
Date: Wed, 8 Jul 2015 22:59:36 -0700	[thread overview]
Message-ID: <20150709055936.GA28488@kroah.com> (raw)
In-Reply-To: <1436410257-20356-1-git-send-email-ronit.crj@gmail.com>

On Thu, Jul 09, 2015 at 08:20:57AM +0530, rcodin wrote:
> From: Ronit Halder <ronit.crj@gmail.com>
> 
> Fixed a coding style issue.
> 
> Signed-off-by: Ronit Halder <ronit.crj@gmail.com>
> ---
>  drivers/staging/android/ion/ion.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c
> index 6f48112..e44f5e6 100644
> --- a/drivers/staging/android/ion/ion.c
> +++ b/drivers/staging/android/ion/ion.c
> @@ -1106,6 +1106,7 @@ struct dma_buf *ion_share_dma_buf(struct ion_client *client,
>  	struct ion_buffer *buffer;
>  	struct dma_buf *dmabuf;
>  	bool valid_handle;
> +
>  	DEFINE_DMA_BUF_EXPORT_INFO(exp_info);

This is a false positive and has been rejected so many times it's really
getting old...

  parent reply	other threads:[~2015-07-09  5:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  2:50 [PATCH] Staging: android: ion: fixed a blank line after declarations coding style issue rcodin
2015-07-09  5:35 ` Sudip Mukherjee
2015-07-09  5:58   ` Ronit Halder
2015-07-09  5:59 ` Greg KH [this message]
2015-07-09  9:57   ` Joe Perches
  -- strict thread matches above, loose matches on Subject: below --
2015-07-09  5:33 Ronit Halder

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=20150709055936.GA28488@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=elfring@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mitchelh@codeaurora.org \
    --cc=riandrews@android.com \
    --cc=ronit.crj@gmail.com \
    --cc=sumit.semwal@linaro.org \
    --cc=tranmanphong@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.