All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: regmap: Separate regmap dev initialization
Date: Tue, 18 Feb 2014 12:59:52 +0000	[thread overview]
Message-ID: <20140218125952.GK26776@mwanda> (raw)
In-Reply-To: <20140218122410.GA9825@elgon.mountain>

On Tue, Feb 18, 2014 at 01:33:30PM +0100, Michal Simek wrote:
> Hi Dan,
> 
> On 02/18/2014 01:24 PM, Dan Carpenter wrote:
> > Hello Michal Simek,
> > 
> > The patch 6cfec04bcc05: "regmap: Separate regmap dev initialization"
> > from Feb 10, 2014, leads to the following static checker warning:
> > 
> > 	drivers/base/regmap/regmap.c:765 regmap_init()
> > 	warn: add curly braces?
> > 
> > drivers/base/regmap/regmap.c
> >    759          ret = regcache_init(map, config);
> >    760          if (ret != 0)
> >    761                  goto err_range;
> >    762  
> >    763          if (dev)
> >    764                  ret = regmap_attach_dev(dev, map, config);
> >    765                  if (ret != 0)
> >    766                          goto err_regcache;
> > 
> > Please add curly braces or adjust the indenting to not confuse the
> > static checkers.
> 
> I am aware about this. Mark has already applied RFC to any his branch
> :-(. I can send v2 but it is up to Mark if he wants to fix it or not.
> 

Oh, crap.  Sorry, I reported this twice.  I didn't mean to do that.

I normally grep my outbox to avoid this but I had a typo in my grep this
time.

regards,
dan carpenter


  parent reply	other threads:[~2014-02-18 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 12:24 regmap: Separate regmap dev initialization Dan Carpenter
2014-02-18 12:33 ` Michal Simek
2014-02-18 12:59 ` Dan Carpenter [this message]
2014-02-18 13:10 ` Michal Simek

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=20140218125952.GK26776@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.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 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.