From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Rob Herring <robh+dt@kernel.org>, devicetree@vger.kernel.org
Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Yu Chen <chenyu56@huawei.com>,
Anitha Chrisanthus <anitha.chrisanthus@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Joe Perches <joe@perches.com>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH RESEND 0/3] Rectify file references for dt-bindings in MAINTAINERS
Date: Mon, 19 Apr 2021 11:26:06 +0200 [thread overview]
Message-ID: <20210419092609.3692-1-lukas.bulwahn@gmail.com> (raw)
Hi Rob,
here is a patch series that cleans up all file references for dt-bindings
in MAINTAINERS. It applies cleanly on next-20210416.
This is a resend of the still relevant patches from the first submission
of the patch series [see Link] on 2021-03-15.
Could you pick this series for your devicetree bindings tree?
No functional change, just cleaning up MAINTAINERS.
Lukas
Link: https://lore.kernel.org/lkml/20210315160451.7469-1-lukas.bulwahn@gmail.com/
Adjustment from original to resend version:
- drop subsumed patches
Lukas Bulwahn (3):
MAINTAINERS: rectify entry for ARM/TOSHIBA VISCONTI ARCHITECTURE
MAINTAINERS: rectify entry for HIKEY960 ONBOARD USB GPIO HUB DRIVER
MAINTAINERS: rectify entry for INTEL KEEM BAY DRM DRIVER
MAINTAINERS | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2021-04-19 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 9:26 Lukas Bulwahn [this message]
2021-04-19 9:26 ` [PATCH 1/3] MAINTAINERS: rectify entry for ARM/TOSHIBA VISCONTI ARCHITECTURE Lukas Bulwahn
2021-04-19 23:28 ` Nobuhiro Iwamatsu
2021-04-19 9:26 ` [PATCH 2/3] MAINTAINERS: rectify entry for HIKEY960 ONBOARD USB GPIO HUB DRIVER Lukas Bulwahn
2021-04-19 23:39 ` Nobuhiro Iwamatsu
2021-04-19 9:26 ` [PATCH 3/3] MAINTAINERS: rectify entry for INTEL KEEM BAY DRM DRIVER Lukas Bulwahn
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=20210419092609.3692-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anitha.chrisanthus@intel.com \
--cc=chenyu56@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=robh+dt@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).