All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms+renesas@verge.net.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: RE: [PATCH] i2c: riic: remove clock and frequency restrictions
Date: Fri, 27 Oct 2017 15:37:14 +0000	[thread overview]
Message-ID: <SG2PR06MB116574A2F2C6B7535415957B8A5A0@SG2PR06MB1165.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20171026203622.hyala2lxsjpdshnh@ninjato>

On Thursday, October 26, 2017, linux-renesas-soc-owner@vger.kernel.org wrote:
> > I ran checkpatch and fixed everything it found, but it didn't flag that
> one.
> >
> >
> > $ scripts/checkpatch.pl z_patches/riic/S4V1/*
> > total: 0 errors, 0 warnings, 169 lines checked
> 
> with "--strict" it will find it.

Yes, then it finds other ones too that you missed.

So for my v2 submission, it passes with --strict.


Chris

      reply	other threads:[~2017-10-27 15:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 14:04 [PATCH] i2c: riic: remove clock and frequency restrictions Chris Brandt
2017-10-18 14:25 ` Geert Uytterhoeven
2017-10-18 14:25   ` Geert Uytterhoeven
2017-10-18 15:10   ` Chris Brandt
2017-10-18 15:14     ` Geert Uytterhoeven
2017-10-18 15:47       ` Chris Brandt
2017-10-18 16:37 ` Wolfram Sang
2017-10-18 16:41   ` Chris Brandt
2017-10-18 16:44     ` Wolfram Sang
2017-10-26 20:36     ` Wolfram Sang
2017-10-27 15:37       ` Chris Brandt [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=SG2PR06MB116574A2F2C6B7535415957B8A5A0@SG2PR06MB1165.apcprd06.prod.outlook.com \
    --to=chris.brandt@renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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.