All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Junsu Shin <jjunes0@gmail.com>,
	devel@driverdev.osuosl.org, boris.brezillon@free-electrons.com,
	mchehab@osg.samsung.com, linux-kernel@vger.kernel.org,
	prabhakar.csengg@gmail.com, hans.verkuil@cisco.com,
	laurent.pinchart@ideasonboard.com, s.nawrocki@samsung.com,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 1/1] Staging: media: davinci_vpfe: fix over 80 characters coding style issue.
Date: Sat, 8 Aug 2015 08:42:59 -0700	[thread overview]
Message-ID: <20150808154259.GD11851@kroah.com> (raw)
In-Reply-To: <20150808101218.GA1301@sudip-pc>

On Sat, Aug 08, 2015 at 03:42:18PM +0530, Sudip Mukherjee wrote:
> On Sat, Aug 08, 2015 at 01:55:02AM -0500, Junsu Shin wrote:
> > 
> > On 08/06/2015 11:45 PM, Sudip Mukherjee wrote:
> > > On Thu, Aug 06, 2015 at 09:55:54PM -0500, Junsu Shin wrote:
> > > 
> <snip>
> > 
> > Thanks for pointing it out.
> > Again, this is a patch to the dm365_ipipe.c that fixes over 80 characters warning detected by the script.
> > This time I fixed up the indentation issue claimed in the previous one.
> > Signed-off-by: Junsu Shin <jjunes0@gmail.com>
> > ---
> Greg will not accept patches like this way. please send it as v2.

Greg does not accept drivers/staging/media/* patches, but anyway, no one
will accept a patch in this format, as you say.

thanks,

greg k-h

  reply	other threads:[~2015-08-08 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  2:55 [PATCH 1/1] Staging: media: davinci_vpfe: fix over 80 characters coding style issue Junsu Shin
2015-08-07  4:45 ` Sudip Mukherjee
2015-08-08  6:55   ` Junsu Shin
2015-08-08 10:12     ` Sudip Mukherjee
2015-08-08 15:42       ` Greg KH [this message]
2015-08-08 17:06         ` Joe Perches

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=20150808154259.GD11851@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hans.verkuil@cisco.com \
    --cc=jjunes0@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sudipm.mukherjee@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.