From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org
Cc: Imre Kaloz <kaloz@openwrt.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Bartosz Golaszewski <brgl@bgdev.pl>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust ARM/INTEL IXP4XX ARM ARCHITECTURE to ixp4xx clean-up
Date: Tue, 14 Jun 2022 21:28:57 +0200 [thread overview]
Message-ID: <475873e3-4166-4e34-7ccc-363dd8963cce@linaro.org> (raw)
In-Reply-To: <20220601050200.22213-1-lukas.bulwahn@gmail.com>
On 01/06/2022 07:02, Lukas Bulwahn wrote:
> Commit c83227a5d05e ("irq/gpio: ixp4xx: Drop boardfile probe path") and
> commit 155e4306107f ("clocksource/drivers/ixp4xx: Drop boardfile probe
> path") remove files include/linux/irqchip/irq-ixp4xx.h and
> include/linux/platform_data/timer-ixp4xx.h, but miss to adjust MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about
> broken references.
>
> Remove file entries for those files in ARM/INTEL IXP4XX ARM ARCHITECTURE.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
> Linus, please pick this minor non-urgent clean-up patch for ixp4xx arm.
>
> MAINTAINERS | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 58e751b9346e..e0f5895feb6b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2196,8 +2196,6 @@ F: drivers/clocksource/timer-ixp4xx.c
> F: drivers/crypto/ixp4xx_crypto.c
> F: drivers/gpio/gpio-ixp4xx.c
> F: drivers/irqchip/irq-ixp4xx.c
> -F: include/linux/irqchip/irq-ixp4xx.h
> -F: include/linux/platform_data/timer-ixp4xx.h
>
> ARM/INTEL KEEMBAY ARCHITECTURE
> M: Paul J. Murphy <paul.j.murphy@intel.com>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2022-06-14 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 5:02 Lukas Bulwahn
2022-06-14 19:28 ` Daniel Lezcano [this message]
2022-06-23 20:31 ` Bartosz Golaszewski
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=475873e3-4166-4e34-7ccc-363dd8963cce@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=brgl@bgdev.pl \
--cc=kaloz@openwrt.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=khalasa@piap.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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®