From: Joe Perches <joe@perches.com>
To: "Daniel Vetter" <daniel@ffwll.ch>,
"Christian König" <christian.koenig@amd.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
intel-gfx@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Sebastian Duda <sebastian.duda@fau.de>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] MAINTAINERS: adjust to reservation.h renaming
Date: Fri, 06 Mar 2020 02:56:06 -0800 [thread overview]
Message-ID: <155f99baffe11836fc9d794ff297bdcee7831050.camel@perches.com> (raw)
In-Reply-To: <20200306103946.GT2363188@phenom.ffwll.local>
On Fri, 2020-03-06 at 11:39 +0100, Daniel Vetter wrote:
> On Wed, Mar 04, 2020 at 01:08:32PM +0100, Christian König wrote:
> > Am 04.03.20 um 13:07 schrieb Lukas Bulwahn:
> > > Commit 52791eeec1d9 ("dma-buf: rename reservation_object to dma_resv")
> > > renamed include/linux/reservation.h to include/linux/dma-resv.h, but
> > > missed the reference in the MAINTAINERS entry.
> > >
> > > Since then, ./scripts/get_maintainer.pl --self-test complains:
> > >
> > > warning: no file matches F: include/linux/reservation.h
> > >
> > > Adjust the DMA BUFFER SHARING FRAMEWORK entry in MAINTAINERS.
> > >
> > > Co-developed-by: Sebastian Duda <sebastian.duda@fau.de>
> > > Signed-off-by: Sebastian Duda <sebastian.duda@fau.de>
> > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> >
> > Reviewed-by: Christian König <christian.koenig@amd.com>
>
> You'll push this too?
> -Daniel
>
> > > ---
> > > Christian, please pick this patch.
> > > applies cleanly on current master and next-20200303
> > >
> > > MAINTAINERS | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 6158a143a13e..3d6cb2789c9e 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -5022,7 +5022,7 @@ L: dri-devel@lists.freedesktop.org
> > > L: linaro-mm-sig@lists.linaro.org (moderated for non-subscribers)
> > > F: drivers/dma-buf/
> > > F: include/linux/dma-buf*
> > > -F: include/linux/reservation.h
> > > +F: include/linux/dma-resv.h
> > > F: include/linux/*fence.h
> > > F: Documentation/driver-api/dma-buf.rst
> > > K: dma_(buf|fence|resv)
Slightly unrelated:
The K: entry matches a lot of other things
and may have a lot of false positive matches
like any variable named dma_buffer
This should also use (?:...) to avoid a perl
capture group.
Perhaps:
K: '\bdma_(?:buf|fence|resv)\b'
next prev parent reply other threads:[~2020-03-06 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 12:07 [PATCH] MAINTAINERS: adjust to reservation.h renaming Lukas Bulwahn
2020-03-04 12:08 ` Christian König
2020-03-06 10:39 ` [Intel-gfx] " Daniel Vetter
2020-03-06 10:56 ` Joe Perches [this message]
2020-03-16 9:50 ` Daniel Vetter
2020-03-16 9:56 ` 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=155f99baffe11836fc9d794ff297bdcee7831050.camel@perches.com \
--to=joe@perches.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=sebastian.duda@fau.de \
--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).