Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2] checkpatch.pl: seed camelcase from the provided kernel tree root
Date: Wed, 31 Aug 2016 20:26:51 -0700	[thread overview]
Message-ID: <1472700411.4176.83.camel@perches.com> (raw)
In-Reply-To: <1472699862.2453.18.camel@intel.com>

On Wed, 2016-08-31 at 20:17 -0700, Jeff Kirsher wrote:

> I thought you got $0.02 for every checkpatch.pl warning and $0.05 for every
> error found? :-)

Well, it's nice to know some credits are accruing in
some virtual bank. ?Unfortunate for me that it's like
the Hotel California Bank though.

> > I don't look at scripts with checkpatch.
> > I think it's really only useful for .[ch] files.
> So should a modification be made to anything in scripts/* for when
> checkpatch.pl is run? ?I know that there are *special* rules for
> drivers/net/*, so it should be easy to apply whatever checks are pertinent
> for scripts/*?

I think scripts should rely a little on the skill
and intelligence of the user.

I have a hammer so let's go fishing, etc...

cheers, ?Joe

      reply	other threads:[~2016-09-01  3:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 21:00 [Intel-wired-lan] [PATCH v2] checkpatch.pl: seed camelcase from the provided kernel tree root Jacob Keller
2016-08-31 20:27 ` Brown, Aaron F
2016-08-31 22:37   ` Keller, Jacob E
2016-09-01  1:04     ` Brown, Aaron F
2016-09-01  2:33       ` Jeff Kirsher
2016-09-01  2:46         ` Joe Perches
2016-09-01  3:17           ` Jeff Kirsher
2016-09-01  3:26             ` Joe Perches [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=1472700411.4176.83.camel@perches.com \
    --to=joe@perches.com \
    --cc=intel-wired-lan@osuosl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox