From: Joe Perches <joe@perches.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Grant Likely <grant.likely@secretlab.ca>,
Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [PATCH 2/3] MAINTAINERS: Document new "K:" entry type
Date: Mon, 12 Oct 2009 04:35:31 -0700 [thread overview]
Message-ID: <1255347331.1839.41.camel@Joe-Laptop.home> (raw)
In-Reply-To: <alpine.LRH.2.00.0910121211250.12171@twin.jikos.cz>
On Mon, 2009-10-12 at 12:14 +0200, Jiri Kosina wrote:
> On Fri, 9 Oct 2009, Joe Perches wrote:
> > + K: Keyword perl extended regex pattern to match content in a
> > + patch or file. For instance:
> > + K: of_get_profile
> > + matches patches or files that contain "of_get_profile"
> > + K: \b(printk|pr_(info|err))\b
> > + matches patches or files that contain one or more of the words
> > + printk, pr_info or pr_err
> What expressions do you expect people will be using here?
Keywords or keyword initiators specific to a facility
that's used kernel-wide.
> (the example with printk() doesn't really demonstrate usefulness of this).
A useful, simple example would be cheerfully substituted.
maybe:
K: \b(AUDIT|audit)_
next prev parent reply other threads:[~2009-10-12 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 6:05 [PATCH 0/3] MAINTAINERS: Add and support "K:" keyword Joe Perches
2009-10-10 6:05 ` [PATCH 1/3] scripts/get_maintainer.pl: Add patch/file search for keywords Joe Perches
2009-10-19 9:41 ` Wolfram Sang
2009-10-19 15:47 ` Joe Perches
2009-10-10 6:05 ` [PATCH 2/3] MAINTAINERS: Document new "K:" entry type Joe Perches
2009-10-12 10:14 ` Jiri Kosina
2009-10-12 11:35 ` Joe Perches [this message]
2009-10-10 6:05 ` [PATCH 3/3] MAINTAINERS: Add OPEN FIRMWARE DEVICE TREE section Joe Perches
2009-10-10 6:33 ` Grant Likely
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=1255347331.1839.41.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=avorontsov@ru.mvista.com \
--cc=grant.likely@secretlab.ca \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=w.sang@pengutronix.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
all inboxes | Powered by JetHome®