All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Elise Lennion <elise.lennion@gmail.com>
Cc: vaibhav.sr@gmail.com, mgreer@animalcreek.com, johan@kernel.org,
	elder@kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 3/7] staging: greybus: Add blank line after variable declarations.
Date: Wed, 12 Oct 2016 15:22:02 +0200	[thread overview]
Message-ID: <20161012132202.GA22338@kroah.com> (raw)
In-Reply-To: <20161011031232.GA21944@lennorien.com>

On Tue, Oct 11, 2016 at 12:12:32AM -0300, Elise Lennion wrote:
> Fix checkpatch warning:
> 
> WARNING: Missing a blank line after declarations
> 
> Signed-off-by: Elise Lennion <elise.lennion@gmail.com>
> ---
>  drivers/staging/greybus/audio_topology.c | 1 +
>  1 file changed, 1 insertion(+)

This subject: is the same as your previous patch in the series :(


      reply	other threads:[~2016-10-12 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11  3:12 [PATCH 3/7] staging: greybus: Add blank line after variable declarations Elise Lennion
2016-10-12 13:22 ` Greg KH [this message]

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=20161012132202.GA22338@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=elder@kernel.org \
    --cc=elise.lennion@gmail.com \
    --cc=johan@kernel.org \
    --cc=mgreer@animalcreek.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=vaibhav.sr@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.