public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Avraham Shukron <avraham.shukron@gmail.com>
Cc: laurent.pinchart@ideasonboard.com, mchehab@kernel.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3 1/2] staging: omap4iss: fix multiline comment style
Date: Thu, 9 Feb 2017 12:06:21 +0100	[thread overview]
Message-ID: <20170209110621.GA11988@kroah.com> (raw)
In-Reply-To: <1e46dc3f0630eae3b531ae3a03bc65bebf5bbfc0.1486413695.git.avraham.shukron@gmail.com>

On Tue, Feb 07, 2017 at 05:40:57PM +0200, Avraham Shukron wrote:
> Signed-off-by: Avraham Shukron <avraham.shukron@gmail.com>
> ---
>  drivers/staging/media/omap4iss/iss_video.c | 38 ++++++++++++++++++++----------
>  1 file changed, 25 insertions(+), 13 deletions(-)

Again, I don't take patches with no changelog text :(

  parent reply	other threads:[~2017-02-09 11:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 18:00 [PATCH] Staging: omap4iss: fix coding style issues Avraham Shukron
2017-01-29  7:31 ` Ozgur Karatas
2017-01-29 22:42   ` Avraham Shukron
2017-01-30 17:47 ` Laurent Pinchart
2017-01-31 10:42   ` Sakari Ailus
2017-01-31 10:46     ` Laurent Pinchart
2017-02-06 17:58       ` [PATCH v2] Staging: omap4iss: Fix " Avraham Shukron
2017-02-07  8:12         ` Greg KH
2017-02-07 15:40           ` [PATCH v3 1/2] staging: omap4iss: fix multiline comment style Avraham Shukron
2017-02-07 15:40             ` [PATCH v3 2/2] staging: omap4iss: fix coding style issue Avraham Shukron
2017-02-09 11:06             ` Greg KH [this message]
2017-02-09 16:57               ` [PATCH v4 1/2] staging: omap4iss: fix multiline comment style Avraham Shukron
2017-02-09 17:01                 ` [PATCH v4 2/2] staging: omap4iss: fix coding style issue Avraham Shukron
2017-02-10  7:48                 ` [PATCH v4 1/2] staging: omap4iss: fix multiline comment style Laurent Pinchart

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=20170209110621.GA11988@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=avraham.shukron@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /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