From: Joe Perches <joe@perches.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>
Cc: linaro-mm-sig@lists.linaro.org,
Daniel Vetter <daniel.vetter@intel.com>,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Better regex for dma_buf|fence|resv
Date: Tue, 17 Mar 2020 05:49:27 -0700 [thread overview]
Message-ID: <52f737a95e0e50d3f556f8ebf3677f99683ee70b.camel@perches.com> (raw)
In-Reply-To: <20200317071547.1008622-1-daniel.vetter@ffwll.ch>
On Tue, 2020-03-17 at 08:15 +0100, Daniel Vetter wrote:
> We're getting some random other stuff that we're not relly interested
> in, so match only word boundaries. Also avoid the capture group while
> at it.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -5025,7 +5025,7 @@ F: include/linux/dma-buf*
> F: include/linux/reservation.h
> F: include/linux/*fence.h
> F: Documentation/driver-api/dma-buf.rst
> -K: dma_(buf|fence|resv)
> +K: '\bdma_(?:buf|fence|resv)\b'
You don't want the single quotes in the K: entry
K: \bdma_(?:buf|fence|resv)\b
My mistake for adding them in the initial suggestion.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-17 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 7:15 [PATCH] MAINTAINERS: Better regex for dma_buf|fence|resv Daniel Vetter
2020-03-17 8:17 ` Sam Ravnborg
2020-03-17 12:49 ` Joe Perches [this message]
2020-03-17 17:06 Daniel Vetter
2020-03-17 20:56 Daniel Vetter
2020-03-18 15:46 ` Sumit Semwal
2020-03-18 16:53 ` Daniel Vetter
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=52f737a95e0e50d3f556f8ebf3677f99683ee70b.camel@perches.com \
--to=joe@perches.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).