All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Colic <colic.christian@gmail.com>
Cc: soren.brinkmann@xilinx.com, devendra.aaru@gmail.com,
	sboyd@codeaurora.org, andnlnbn18@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: clocking-wizard: add blank line after struct declaration.
Date: Sun, 7 Feb 2016 20:06:16 -0800	[thread overview]
Message-ID: <20160208040616.GA19127@kroah.com> (raw)
In-Reply-To: <20151201125601.GA21005@lenovo>

On Tue, Dec 01, 2015 at 01:56:01PM +0100, Christian Colic wrote:
> Add blank line after struct declaration to fix checkpatch check.
> 
> Signed-off-by: Christian Colic <colic.christian@gmail.com>
> Reviewed-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> 
> ---
>  drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c b/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c
> index b8e2f61..1cbf5eb 100644
> --- a/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c
> +++ b/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c
> @@ -71,6 +71,7 @@ struct clk_wzrd {
>  	int speed_grade;
>  	bool suspended;
>  };
> +
>  #define to_clk_wzrd(_nb) container_of(_nb, struct clk_wzrd, nb)
>  
>  /* maximum frequencies for input/output clocks per speed grade */
> -- 
> 2.5.0
> 

Doesn't apply :(

  parent reply	other threads:[~2016-02-08  4:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 12:56 [PATCH] staging: clocking-wizard: add blank line after struct declaration Christian Colic
2015-12-01 16:52 ` Sören Brinkmann
2016-02-08  4:06 ` Greg KH [this message]
2016-02-08  4:06   ` Greg KH

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=20160208040616.GA19127@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andnlnbn18@gmail.com \
    --cc=colic.christian@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devendra.aaru@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=soren.brinkmann@xilinx.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.