All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] next 17 checkpatch patches
Date: Sun, 08 Jan 2012 17:43:03 +0000	[thread overview]
Message-ID: <20120108174303.GB23387@ericsson.com> (raw)
In-Reply-To: <CACW_hTZ1cYLXJS3cpsQ8fDTrr40PqPc654892a7FRR7VNng9GA@mail.gmail.com>

Hi Frans,

On Sun, Jan 08, 2012 at 11:23:29AM -0500, Frans Meulenbroeks wrote:
> Hi all,
> 
> I've examined some more files for checkpatch problems.
> After this I'll post 17 patches.
> checkpatch lists no problems with them
> They are all compile tested
> 
> Within the files I address some problems are not resolved:
> 
> There were a few places where lines were a few chars too long but were not easy
> to break
> (e.g. because it was a long URL).
> 
> There was one place where a macro needed a do while(0); didn't peek at that one
> yet
> 
> And on a place there were two assignments in an if. Previously on a different
> case Jean told me
> it was intentional, therefore I did not touch it
> (I did touch a few places where there was a single assignment within an if).
> 
> I might be doing a few more of these later today or next few days.
> There are still about 50 files with errors or warning left. However, I have
> kinda picked the low hanging fruit (= the files that only have a few errors).
> 
> Best regards, Frans
> 
> PS: I did not bother to report the details of the checkpatch errors that were
> fixed in the commit message.

Would be great if you could do that, though. Not in the headline, but in the text.
Otherwise, I or Jean would have to do it, for which we don't necessarily have the time.

> For some of the files that still are to be done that would result in commit
> messages of > 100 lines (and not too useful).

That is why you do it in the explanation, not in the headline ...

Another nitpick: We commonly use

hwmon: (drivername) This is a commit message

as commit headline. Not much difference, but it would save us a couple of minutes
if you could do that as well.

Patches look good, except for the last one for which I sent you separate feedback.
Would be great if you could resubmit the series with the above changes.

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2012-01-08 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 16:23 [lm-sensors] next 17 checkpatch patches Frans Meulenbroeks
2012-01-08 17:43 ` Guenter Roeck [this message]
2012-01-08 18:15 ` Frans Meulenbroeks
2012-01-08 18:58 ` Guenter Roeck

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=20120108174303.GB23387@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=lm-sensors@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.