From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] power: twl6030: fix code refactoring
Date: Sat, 15 Oct 2016 19:48:48 +0200 [thread overview]
Message-ID: <1476553728.1127.2.camel@paulk.fr> (raw)
In-Reply-To: <CAKP5S=0YUgE3+XaGsEgQo4MFNgv4UHc5HGouSHzZPAU1J3mKvg@mail.gmail.com>
Hi,
Le samedi 15 octobre 2016 ? 20:41 +0300, Nicolae Rosia a ?crit?:
> Hi,
>
> On Fri, Oct 14, 2016 at 4:28 PM, Paul Kocialkowski <contact@paulk.fr> wrote:
> >
> > Le jeudi 13 octobre 2016 ? 13:47 +0300, Nicolae Rosia a ?crit :
> > >
> > > From: Nicolae Rosia <nicolae.rosia@gmail.com>
> > >
> > > Commit a85362fb3e1fc7833723accddbbae431091d06b8 refactored the code
> > > but the register read ended up in the wrong if branch.
> > > Currently, the else branch checks a variable which is always 0.
> >
> > Good catch! Sorry for including that regression in the first place, I should
> > have checked the patch more thoroughly.
> No worries!
>
> >
> > See comment below.
> > The indentation before &value is inconsistent with what is done in the rest
> > of
> > the file. I think you should either just move the line as it was or only use
> > one
> > extra tab indent for the new line. Since this file breaks the 80 chars limit
> > in
> > a few places, I would tend to prefer the former.
> >
> checkpatch.pl was complaining, that's why I formatted it.
Then I think you should fix the rest of the file accordingly.
It doesn't make sense to introduce a variation in the coding style, as it
creates inconsistency. IMO this is worse than having only subsequent changes
conform to the global U-Boot coding style.
> @Tom Rini, can you apply it either way?
>
> Best regards,
> Nicolae
--
Paul Kocialkowski, developer of free digital technology at the lower levels
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161015/af328088/attachment.sig>
next prev parent reply other threads:[~2016-10-15 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 10:47 [U-Boot] [PATCH] power: twl6030: fix code refactoring Nicolae Rosia
2016-10-13 16:54 ` Tom Rini
2016-10-14 13:28 ` Paul Kocialkowski
2016-10-15 17:41 ` Nicolae Rosia
2016-10-15 17:48 ` Tom Rini
2016-10-17 17:03 ` Nicolae Rosia
2016-10-17 18:15 ` Tom Rini
2016-10-15 17:48 ` Paul Kocialkowski [this message]
2016-10-24 15:24 ` [U-Boot] " Tom Rini
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=1476553728.1127.2.camel@paulk.fr \
--to=contact@paulk.fr \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox