[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.0910121211250.12171@twin.jikos.cz>
Date: Mon, 12 Oct 2009 12:14:05 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Joe Perches <joe@...ches.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Wolfram Sang <w.sang@...gutronix.de>,
Grant Likely <grant.likely@...retlab.ca>,
Anton Vorontsov <avorontsov@...mvista.com>
Subject: Re: [PATCH 2/3] MAINTAINERS: Document new "K:" entry type
On Fri, 9 Oct 2009, Joe Perches wrote:
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e1da925..4407de2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -65,43 +65,51 @@ trivial patch so apply some common sense.
>
> 8. Happy hacking.
>
> - -----------------------------------
> -
> -Maintainers List (try to look for most precise areas first)
> +Descriptions of section entries:
[ ... ]
> + 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
> + One regex pattern per line. Multiple K: lines acceptable.
What expressions do you expect people will be using here? (the example
with printk() doesn't really demonstrate usefulness of this).
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists