From: Boris Brezillon <boris.brezillon@collabora.com>
To: Joe Perches <joe@perches.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
linux-i3c@lists.infradead.org,
Boris Brezillon <bbrezillon@kernel.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Bad file pattern in MAINTAINERS section 'I3C SUBSYSTEM'
Date: Sat, 30 Mar 2019 08:51:11 +0100 [thread overview]
Message-ID: <20190330085111.71a04fd9@collabora.com> (raw)
In-Reply-To: <20190325212519.26558-1-joe@perches.com>
Hello Joe,
On Mon, 25 Mar 2019 14:25:19 -0700
Joe Perches <joe@perches.com> wrote:
> A file pattern line in this section of the MAINTAINERS file in linux-next
> does not have a match in the linux source files.
>
> This could occur because a matching filename was never added, was deleted
> or renamed in some other commit.
This is a leftover of previous versions of the patch series where
things were added to include/dt-bindings/i3c/.
>
> The commits that added and if found renamed or removed the file pattern
> are shown below.
>
> Please fix this defect appropriately.
I'll fix that. Thanks for reporting the problem.
Boris
>
> 1: ---------------------------------------------------------------------------
>
> linux-next MAINTAINERS section:
>
> 7333 I3C SUBSYSTEM
> 7334 M: Boris Brezillon <bbrezillon@kernel.org>
> 7335 L: linux-i3c@lists.infradead.org
> 7336 C: irc://chat.freenode.net/linux-i3c
> 7337 T: git git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git
> 7338 S: Maintained
> 7339 F: Documentation/ABI/testing/sysfs-bus-i3c
> 7340 F: Documentation/devicetree/bindings/i3c/
> 7341 F: Documentation/driver-api/i3c
> 7342 F: drivers/i3c/
> 7343 F: include/linux/i3c/
> --> 7344 F: include/dt-bindings/i3c/
>
> 2: ---------------------------------------------------------------------------
>
> The most recent commit that added or modified file pattern 'include/dt-bindings/i3c/':
>
> commit 4f26d06669619b960aa7246378dcdf1690c97384
> Author: Boris Brezillon <boris.brezillon@bootlin.com>
> Date: Fri Mar 23 11:38:16 2018 +0100
>
> MAINTAINERS: Add myself as the I3C subsystem maintainer
>
> Create an entry for the I3C subsystem and mark it as maintained by me.
> There's no official git repository, patchwork instance, mailing list or
> website yet, but this will be added after the subsystem has been
> accepted.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> MAINTAINERS | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> 3: ---------------------------------------------------------------------------
>
> No commit with file pattern 'include/dt-bindings/i3c/' was found
>
> _______________________________________________
> linux-i3c mailing list
> linux-i3c@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-i3c
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2019-03-30 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:25 ` Bad file pattern in MAINTAINERS section 'I3C SUBSYSTEM' Joe Perches
2019-03-30 7:51 ` Boris Brezillon [this message]
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=20190330085111.71a04fd9@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@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).