From: Joe Perches <joe@perches.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"apw@canonical.com" <apw@canonical.com>,
Joe Perches <golf@perches.com>
Cc: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: fix camel case seeding when run with --root
Date: Wed, 20 Mar 2019 14:18:21 -0700 [thread overview]
Message-ID: <52138d9db7b1765133f21fe08b0f3ad37da9d799.camel@perches.com> (raw)
In-Reply-To: <02874ECE860811409154E81DA85FBB589232E64D@ORSMSX121.amr.corp.intel.com>
On Wed, 2019-03-20 at 20:09 +0000, Keller, Jacob E wrote:
> > -----Original Message-----
> > From: Keller, Jacob E
> > Sent: Thursday, March 14, 2019 6:04 PM
> > To: linux-kernel@vger.kernel.org
> > Cc: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>; netdev@vger.kernel.org;
> > Keller, Jacob E <jacob.e.keller@intel.com>; joe@perches.com
> > Subject: [PATCH] checkpatch: fix camel case seeding when run with --root
> >
> > checkpatch.pl avoids warning about camel case of some definitions by
> > seeding a file that tracks all of the currently committed camel case
> > definitions.
> >
> > To build this seed file, checkpatch.pl decides between using git or the
> > --root parameter.
> >
> > This works as long as you don't run checkpatch.pl from within
> > a different git tree that is not the Linux kernel.
Odd use case, but I'll forward it on as it doesn't
seem to have any other effect.
cheers, Joe
next prev parent reply other threads:[~2019-03-20 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 1:03 Jacob Keller
2019-03-20 20:09 ` Keller, Jacob E
2019-03-20 21:18 ` Joe Perches [this message]
2019-03-20 22:24 ` Keller, Jacob E
-- strict thread matches above, loose matches on Subject: below --
2019-03-15 1:01 Jacob Keller
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=52138d9db7b1765133f21fe08b0f3ad37da9d799.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=golf@perches.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®