From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Joe Perches <joe@perches.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Duplicated DMA-BUF HEAPS FRAMEWORK in MAINTAINERS on next-20200420
Date: Mon, 20 Apr 2020 10:17:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2004201003340.7417@felia> (raw)
Hi Thomas,
on next-20200420, ./scripts/checkpatch.pl -f MAINTAINERS and
./scripts/parse-maintainers.pl report a number of issues:
WARNING: Misordered MAINTAINERS entry - list file patterns in alphabetic
order
#5059: FILE: MAINTAINERS:5059:
+F: include/linux/dma-resv.h
+F: include/linux/*fence.h
WARNING: Misordered MAINTAINERS entry - list file patterns in alphabetic
order
#5060: FILE: MAINTAINERS:5060:
+F: include/linux/*fence.h
+F: Documentation/driver-api/dma-buf.rst
WARNING: Misordered MAINTAINERS entry - list 'T:' before 'K:'
#5062: FILE: MAINTAINERS:5062:
+K: \bdma_(?:buf|fence|resv)\b
+T: git git://anongit.freedesktop.org/drm/drm-misc
WARNING: Misordered MAINTAINERS entry - list 'L:' before 'S:'
#5073: FILE: MAINTAINERS:5073:
+S: Maintained
+L: linux-media@vger.kernel.org
WARNING: Misordered MAINTAINERS entry - list file patterns in alphabetic
order
#5077: FILE: MAINTAINERS:5077:
+F: include/uapi/linux/dma-heap.h
+F: include/linux/dma-heap.h
WARNING: Misordered MAINTAINERS entry - list file patterns in alphabetic
order
#5078: FILE: MAINTAINERS:5078:
+F: include/linux/dma-heap.h
+F: drivers/dma-buf/dma-heap.c
WARNING: Misordered MAINTAINERS entry - list 'T:' before 'F:'
#5080: FILE: MAINTAINERS:5080:
+F: drivers/dma-buf/heaps/*
+T: git git://anongit.freedesktop.org/drm/drm-misc
Header 'DMA-BUF HEAPS FRAMEWORK' already exists at
./scripts/parse-maintainers.pl line 159, <$file> line 5109.
I tracked this down to commit 08d99b2c23df ("Merge drm/drm-next into
drm-misc-next") visible in next-20200420.
It seems that this commit adds the DMA-BUF HEAPS FRAMEWORK a second time
in its state before the reordering into MAINTAINERS through this merge.
Possibly, you can clean this up? I am happy to support with further
patches if it is clear what we should do here.
Best regards,
Lukas
reply other threads:[~2020-04-20 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.21.2004201003340.7417@felia \
--to=lukas.bulwahn@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.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®