dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Linaro MM SIG <linaro-mm-sig@lists.linaro.org>,
	Joe Perches <joe@perches.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	"open list:DMA BUFFER SHARING FRAMEWORK"
	<linux-media@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Better regex for dma_buf|fence|resv
Date: Wed, 18 Mar 2020 17:53:21 +0100	[thread overview]
Message-ID: <20200318165321.GZ2363188@phenom.ffwll.local> (raw)
In-Reply-To: <CAO_48GH1YkA4mvjyQ=88VRrDPc4Kh8fiFsm-MOaNFfWhhaxfbw@mail.gmail.com>

On Wed, Mar 18, 2020 at 09:16:17PM +0530, Sumit Semwal wrote:
> Hello Daniel,
> 
> Thanks for the patch.
> 
> On Wed, 18 Mar 2020 at 02:26, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >
> > We're getting some random other stuff that we're not really interested
> > in, so match only word boundaries. Also avoid the capture group while
> > at it.
> >
> > Suggested by Joe Perches.
> >
> > Cc: linux-media@vger.kernel.org
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: linaro-mm-sig@lists.linaro.org
> > Cc: Joe Perches <joe@perches.com>
> > Cc: Sumit Semwal <sumit.semwal@linaro.org>
> > Cc: Sam Ravnborg <sam@ravnborg.org>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> 
> Acked-by: Sumit Semwal <sumit.semwal@linaro.org>

Thanks for your ack, patch applied.
-Daniel

> > ---
> > v2: No single quotes in MAINTAINERS (Joe)
> > v3: Fix typo in commit message (Sam)
> > ---
> >  MAINTAINERS | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 3005be638c2c..ed6088a01bfe 100644
> > --- 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
> >  T:     git git://anongit.freedesktop.org/drm/drm-misc
> >
> >  DMA-BUF HEAPS FRAMEWORK
> > --
> > 2.25.1
> >

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-03-18 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 20:56 [PATCH] MAINTAINERS: Better regex for dma_buf|fence|resv Daniel Vetter
2020-03-18 15:46 ` Sumit Semwal
2020-03-18 16:53   ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-17 17:06 Daniel Vetter
2020-03-17  7:15 Daniel Vetter
2020-03-17  8:17 ` Sam Ravnborg
2020-03-17 12:49 ` 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=20200318165321.GZ2363188@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joe@perches.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sumit.semwal@linaro.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).