public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: rcodin <ronit.crj@gmail.com>,
	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: Thu, 09 Jul 2015 02:57:51 -0700	[thread overview]
Message-ID: <1436435871.2682.100.camel@perches.com> (raw)
In-Reply-To: <20150709055936.GA28488@kroah.com>

On Wed, 2015-07-08 at 22:59 -0700, Greg KH wrote:
> On Thu, Jul 09, 2015 at 08:20:57AM +0530, rcodin wrote:
> > Fixed a coding style issue.
[]
> > diff --git 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...

There's a checkpatch patch for that that'll eventually get applied.

https://lkml.org/lkml/2015/7/1/383



  reply	other threads:[~2015-07-09  9:58 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
2015-07-09  9:57   ` Joe Perches [this message]
  -- 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=1436435871.2682.100.camel@perches.com \
    --to=joe@perches.com \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=elfring@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox