public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@linaro.org>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>,
	"Michal Simek" <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Soren Brinkmann" <soren.brinkmann@xilinx.com>
Subject: Re: [PATCH 0/3] clk: zynq: Clean up
Date: Tue, 02 Sep 2014 19:38:44 -0700	[thread overview]
Message-ID: <20140903023844.5251.5476@quantum> (raw)
In-Reply-To: <1409698929-30143-1-git-send-email-soren.brinkmann@xilinx.com>

Quoting Soren Brinkmann (2014-09-02 16:02:06)
> Hi,
> 
> triggered by that discussion whether checkpatch should be used to check
> files, I ran checkpatch on Zynq's clock code. A few of the reported
> issues I found worth fixing.

Applied to clk-next.

Regards,
Mike

> 
>         Thanks,
>         Sören
> 
> Soren Brinkmann (3):
>   clk: zynq: Remove unnecessary OOM message
>   clk: zynq: Remove pointless return at end of void function
>   clk: zynq: Move const initdata into correct code section
> 
>  drivers/clk/zynq/clkc.c | 30 ++++++++++++++----------------
>  drivers/clk/zynq/pll.c  |  4 +---
>  2 files changed, 15 insertions(+), 19 deletions(-)
> 
> -- 
> 2.1.0.1.g27b9230
> 

      parent reply	other threads:[~2014-09-03  2:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 23:02 [PATCH 0/3] clk: zynq: Clean up Soren Brinkmann
2014-09-02 23:02 ` [PATCH 1/3] clk: zynq: Remove unnecessary OOM message Soren Brinkmann
2014-09-02 23:02 ` [PATCH 2/3] clk: zynq: Remove pointless return at end of void function Soren Brinkmann
2014-09-02 23:02 ` [PATCH 3/3] clk: zynq: Move const initdata into correct code section Soren Brinkmann
2014-09-03  2:38 ` Mike Turquette [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=20140903023844.5251.5476@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox