From: Brian Norris <computersforpeace@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: checkpatch.pl false positive: FSF mailing address
Date: Thu, 10 Mar 2016 11:28:18 -0800 [thread overview]
Message-ID: <20160310192818.GA9902@google.com> (raw)
In-Reply-To: <1457637955.3433.17.camel@perches.com>
On Thu, Mar 10, 2016 at 11:25:55AM -0800, Joe Perches wrote:
> On Thu, 2016-03-10 at 11:15 -0800, Brian Norris wrote:
> > On Thu, Mar 10, 2016 at 11:08 AM, Joe Perches <joe@perches.com> wrote:
>
> Hey again Brian.
>
> > > Yeah, it's amusing. It's also likely not something worth
> > > bothering with though as the likelihood of fixing it is low
> > > and eventually the FSF warning will be minimized or removed
> > > as no longer necessary.
> > An easy improvement: don't use "ignore case" for the regex.
>
> Maybe, but:
>
> drivers/pcmcia/bfin_cf_pcmcia.c: * if not, write to the free software foundation,
>
> Of course there's only one of those too.
>
> Mostly, it's a "I just don't care very much" warning.
>
> If you care enough to submit a patch removing the "/i"
> from the regex, please do and cc Andrew Morton too.
Maybe I will.
> > > checkpatch is stupid, false positives will always exist.
>
> I'd almost rather have people understand this.
Then perhaps I'll also patch this note out:
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Regards,
Brian
next prev parent reply other threads:[~2016-03-10 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 19:00 checkpatch.pl false positive: FSF mailing address Brian Norris
2016-03-10 19:08 ` Joe Perches
2016-03-10 19:15 ` Brian Norris
2016-03-10 19:25 ` Joe Perches
2016-03-10 19:28 ` Brian Norris [this message]
2016-03-10 19:34 ` Joe Perches
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=20160310192818.GA9902@google.com \
--to=computersforpeace@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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.