From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Rosin <peda@axentia.se>
Subject: Bad MAINTAINERS pattern in section 'MULTIPLEXER SUBSYSTEM'
Date: Fri, 28 Sep 2018 15:00:55 -0700 [thread overview]
Message-ID: <20180928220055.30772-1-joe@perches.com> (raw)
Please fix this defect appropriately.
linux-next MAINTAINERS section:
9976 MULTIPLEXER SUBSYSTEM
9977 M: Peter Rosin <peda@axentia.se>
9978 S: Maintained
9979 F: Documentation/ABI/testing/sysfs-class-mux*
9980 F: Documentation/devicetree/bindings/mux/
--> 9981 F: include/linux/dt-bindings/mux/
9982 F: include/linux/mux/
9983 F: drivers/mux/
Commit that introduced this:
commit 256ac0375098e50d59c415fcbb561f2927fa8780
Author: Peter Rosin <peda@axentia.se>
Date: Sun May 14 21:51:05 2017 +0200
dt-bindings: document devicetree bindings for mux-controllers and gpio-mux
Allow specifying that a single multiplexer controller can be used to
control several parallel multiplexers, thus enabling sharing of the
multiplexer controller by different consumers.
Add a binding for a first mux controller in the form of a GPIO based mux
controller.
Acked-by: Jonathan Cameron <jic23@kernel.org>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Peter Rosin <peda@axentia.se>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Documentation/devicetree/bindings/mux/gpio-mux.txt | 69 +++++++++
.../devicetree/bindings/mux/mux-controller.txt | 157 +++++++++++++++++++++
MAINTAINERS | 6 +
include/dt-bindings/mux/mux.h | 16 +++
4 files changed, 248 insertions(+)
No commit with include/linux/dt-bindings/mux/ found
next reply other threads:[~2018-09-28 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 22:00 Joe Perches [this message]
2018-10-01 11:41 ` [PATCH] MAINTAINERS: use the correct location for dt-bindings includes for mux Peter Rosin
2018-10-08 21:15 ` Peter Rosin
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=20180928220055.30772-1-joe@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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®